scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-08-28 04:24:58 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
1499 commits 7 branches 7 tags 43 MiB
Commit graph

28 commits

Author SHA1 Message Date
Claude
894fd23334
feat(agents,commands): trigger descriptions + gated workflow upgrades 
- 17 root agents gained 'Use when...' trigger descriptions (<=1024 chars);
  cs-product-analyst placeholder body rewritten around real tools
- 21 commands had invalid YAML frontmatter fixed (unquoted inner colons);
  14 commands gained argument-hint; 6 duplicate commands marked with
  canonical-copy sync comments
- /prd: forcing questions + refuse-to-draft gate + required-sections checklist
- /sprint-plan: capacity math + carry-over check + definition-of-ready gate
- /tdd: rebuilt around the real tdd-guide assets with smoke-tested snippets
- cs-senior-engineer repointed from retired release-manager to
  changelog-generator

https://claude.ai/code/session_019AJddAL1NADWMXsy1qNPQF
 2026-06-11 03:58:42 +00:00
Claude
a088c8ba77
fix: phantom-path sweep — 888 unresolvable references to zero 
A directory reorg added a skills/ path segment; hundreds of references never
followed. This sweep repoints every path-like reference in SKILL.md, agents,
commands, orchestration, and templates to verified on-disk targets:

- 30 root commands + 19 root agents: missing skills/ segment inserted
- 7 c-level persona agents: 17 hallucinated reference filenames substituted
  with the real files (e.g. okr_execution.md -> process_frameworks.md)
- 5 research skills: phantom scripts/office/validate.py step replaced with a
  runnable stdlib zip-integrity check
- email agents: skills frontmatter corrected to productivity/email
- orchestration/ORCHESTRATION.md + templates: stale paths fixed;
  agent-template now requires trigger phrasing in descriptions (root cause)
- 76 more files across engineering, c-level-advisor, compliance-os,
  research-ops, ra-qm, marketing, productivity; dual-publish pairs mirrored
- dead refs dropped/replaced where no target ever existed (REGISTRY.md,
  trend_analyzer.py, cursor-microinteractions.md)

New: scripts/check_paths.py linter (CI gate G1) + narrow allowlist for
teaching examples. Verified: 540 files scanned, 0 unresolvable.

https://claude.ai/code/session_019AJddAL1NADWMXsy1qNPQF
 2026-06-10 14:33:00 +00:00
D4R7HV493R
9885d82df0
feat(marketing): add cs-webinar-marketer agent + /cs:webinar command (#789) 
Adds cs-webinar-marketer agent + /cs:webinar command wiring the webinar-marketing skill (SKILL.md, stdlib funnel scorer, references, templates, evals) under marketing-skill/skills/. Includes a Windows cross-platform fix to scripts/generate-docs.py (normalizes os.sep to forward slashes — verified no-op on Linux) and regenerated docs. Verified: scorer runs (89/100 sample), frontmatter valid, clean merge into dev with no conflicts.
 2026-06-03 16:15:44 +02:00
Claude
5954dfcce1
cleanup(engineering): address remaining 7 polish items from PR #718 bot review 
Bundle of low-medium-severity follow-ups that were deferred when PR #720
landed the 3 blocking bugs. None of these silently break correctness —
they're discoverability, consistency, and convention gaps.

Bugs / code-quality:

1. fullstack_decision_engine.py: asymmetric cadence matching
   `inputs.cadence in target or target in inputs.cadence` produced
   asymmetric results — "per-pr" matched "per-pr-with-gates" but not
   vice versa. Profile cadences are intentional alternatives joined
   by "-or-" (e.g. "weekly-or-on-demand" → {weekly, on-demand}); now
   parsed explicitly with "-with-..." modifier suffixes stripped.

   Verified:
     cadence=per-pr → matches per-pr, per-pr-with-gates, daily-or-per-pr
     cadence=daily  → matches daily-or-per-pr (only)
     cadence=on-demand → matches weekly-or-on-demand

2. fullstack_decision_engine.py: rename weight_total/weight_matched
   to w_total/w_matched. Backend and frontend engines already use the
   short form; this aligns the three files as a family.

3. sync-gemini-skills.py: 3-way name collision in dedup logic
   The naive `if name in seen_names: name = parent-name` handled one
   collision but not two. Three "status" skills under "skills" parent
   dirs produced two entries both named "skills-status". Now suffixes
   with -2, -3, ... so each entry has a unique index name. Eliminates
   the duplicate-name ambiguity surfaced when checking PR #713.

Discoverability:

4. senior-fullstack/SKILL.md: surface fullstack_decision_engine.py in
   the labeled "Tools" section at the top. Previously only mentioned
   inline in the body (5 references buried in the Stack Decision Matrix
   section); not findable when scanning the SKILL.md.

Conventions / v2.8.0 compliance:

5. commands/cs-{fullstack,backend,frontend}-review.md: add explicit
   "## Forcing-question library" section header per the v2.8.0
   convention. Each lists the 7 questions inline with a pointer to
   the canonical reference file.

6. agents/engineering/cs-{fullstack,backend,frontend}-engineer.md:
   alphabetize the specialist list in the description field (annotated
   that workflow body order remains dependency-driven). Makes the
   three agent descriptions consistent as a family.

7. agents/engineering/cs-{backend,frontend}-engineer.md: promote the
   "Cross-agent invocation" content out of Workflow 3 into a dedicated
   "## When invoked as fork target" section with an explicit question-
   skip table per parent agent (cs-fullstack-engineer, cs-cto-advisor,
   cs-vpe-advisor, cs-ciso-advisor for backend; cs-fullstack-engineer,
   cs-content-creator, cs-product-manager for frontend). Closes the
   cross-agent contract gap the bot flagged.

Not changed:

- CLAUDE.md plugin-schema section (already corrected in #715; bot's
  "stale text" claim was incorrect — it was reading the cumulative diff)
- Workflow body specialist order (intentional dependency order; would
  break the SLO-first → API → DB → migration → observability sequence)

Verification:
- All 3 decision engines: --sample → exit 0
- Cadence matching: 3 test cases pass cleanly
- check_plugin_json.py --all → 0 FAIL, 0 WARN, 69 OK
- sync-gemini-skills.py → 392 unique names (was 391 unique / 1 dupe)
 2026-05-21 13:47:08 +00:00
Claude
2c5a793128
feat(engineering): apply karpathy-coder + Matt Pocock to fullstack/frontend/backend 
Audit findings:
- senior-fullstack / senior-frontend / senior-backend SKILL.md files were
  generic role catalogs with no opinionated workflow, no customization
  surface, and no cross-agent invocation contract.
- A 4-person SaaS startup and a 200-engineer enterprise read identical
  recommendations.
- Other agents/skills had no typed surface to orchestrate fullstack /
  frontend / backend lenses.

Per-skill additions (21 new files: 7 x 3 skills):
- scripts/<role>_decision_engine.py - stdlib-only deterministic profile
  picker. Refuses to recommend without Karpathy-#1 core assumptions.
  Surfaces kill criteria. Names human approver chain (never auto-approves).
- profiles/*.json x 4 per skill (12 total) - JSON customization surface.
  Users copy one to <your-org>.json to override defaults.
- references/forcing_questions.md - 7 Matt Pocock forcing questions per
  skill (21 total) with recommended answer + canon citation + kill criterion.
- references/composition_map.md - explicit routing into POWERFUL-tier
  specialists (api-design-reviewer, database-designer, slo-architect,
  performance-profiler, a11y-audit, epic-design, apple-hig-expert, etc.).

Three orchestrator agents (context: fork):
- agents/engineering/cs-fullstack-engineer.md
- agents/engineering/cs-frontend-engineer.md
- agents/engineering/cs-backend-engineer.md
Invokable by other agents via Agent(subagent_type="cs-<role>-engineer", ...).

Four slash commands:
- /cs:fullstack-review, /cs:frontend-review, /cs:backend-review
- /cs:engineer-grill - cross-role 21-question forcing-question runner

Augmented SKILL.md files (additive only - Karpathy #3 surgical):
Each gained 5 new sections: Assumptions & Verifiable Success Criteria
(Karpathy #1+#4), Customization profiles, Composition map, Forcing-question
library, Invocation from other agents and skills.

Verification:
- 12/12 profile JSON files parse cleanly
- 3/3 decision engines pass --help and --sample, exit 0
- 3/3 cs-* agents have valid YAML + context: fork
- 3/3 agent paths resolve from agents/engineering/
- 3/3 commands reference the correct cs-* agent
- 69/69 plugin.json files pass check_plugin_json.py
- Existing SKILL.md content unchanged (additive edits only)

Versions: engineering-team plugin 2.2.3 -> 2.8.1; marketplace entry 2.8.1.

https://claude.ai/code/session_01UyWs4rKccdxUWFcWi6Y8Ly
 2026-05-20 07:24:21 +00:00
Claude
7c54a72d94
chore(v2.7.3): release prep — docs sync + audit fixes + CHANGELOG 
Post-merge sync of v2.7.3 (#679 already in dev). Three things in one
commit:

## 1. /update-docs pipeline (Steps 1-7)

Cross-platform sync verified clean across 3 platforms (.codex 305 /
.gemini 355 / .hermes 305 — aeo + security-guidance present in all
three indexes). 401 → 403 MkDocs pages generated.

**Files refreshed to v2.7.3 / 313 / 46+ / 60+ counts:**

- `.claude-plugin/marketplace.json` — top-level description + metadata
  description + metadata.version (was 2.7.0).
- `CLAUDE.md` — Current Scope line, new v2.7.3 Highlights section,
  footer (Last Updated + Version + Status).
- `README.md` — tagline, badges, Skills Overview row counts (Engineering
  POWERFUL 44 → 45, Marketing 44 → 45 w/ 8 pods), Python Tools count,
  FAQ counts. Hermes footnote ticked v2.7.2 → v2.7.3.
- `docs/index.md` — title, meta description, hero subtitle, grid card.
- `docs/getting-started.md` — meta description, FAQ count.
- `mkdocs.yml` — site_description + 3 nav entries (skill + agent + cmd).
- `marketing-skill/.claude-plugin/plugin.json` — 44 → 45 skills, 7 → 8
  pods, v2.2.3 → v2.7.3.
- `marketing-skill/CLAUDE.md` — 43 → 45 skill count, 32 → 58 Python
  tools, 7 → 8 pods. Added AEO skill to skill map.

## 2. /plugin-audit on both new skills (full 8-phase pipeline)

**aeo (marketing-skill/skills/aeo/)** — PASS WITH WARNINGS:
- Phase 2 Structure: 86.4/GOOD (after auto-fix of YAML frontmatter
  parse error — colon in description value needed quote-wrapping)
- Phase 3 Quality: 52.4/D (validator expects legacy fields v2.7 skills
  don't use — repo-wide pattern, not a defect)
- Phase 4 Scripts: 3/3 PASS
- Phase 5 Security: 2 HIGH NET-EXFIL findings on urllib.request — same
  known false-positive as sister seo-audit skill (URL fetch is core
  functionality for content-audit-by-URL tools, not exfiltration)
- Phase 6 Marketplace: plugin.json valid (v2.7.3, all required fields)
- Phase 7 Ecosystem: indexed in all 3 platforms
- Phase 8 Code Review: 22 workflow sections, refs cite 8/17/37 sources
  (≥7 floor met), 0 broken links, attribution present

**security-guidance (engineering/security-guidance/)** — PASS WITH
WARNINGS:
- Phase 2/3/4: low scores due to hook-plugin layout mismatch with
  script-plugin validators (hook plugins use `hooks/` not `scripts/`
  per Claude Code spec — fundamental structural mismatch, not a defect)
- Phase 5: 6 CRITICAL + 4 HIGH findings are all recursive false-
  positives — auditor detects the hook's OWN pattern-detection strings
  (`"exec("`, `"eval("`, `"yaml.load("` are substring literals used as
  detection rules, NOT actual calls). Verified zero real exec/eval
  calls in the file.
- Phase 6/7: clean (plugin.json valid, hooks.json valid, indexed in
  all 3 platforms, mkdocs nav entry added)
- Phase 8: 291 LOC, syntax valid, clear exit-code contract (0=clean,
  2=block per Claude Code hook spec), session-state caching @ lines
  158-191, 30-day cleanup @ line 163, attribution full, live smoke
  test (`eval(input())` in Write → exit 2 + warning) PASS
- **Real defects: 0.**

## 3. Layout fix (Phase 7 audit catch)

The /plugin-audit Phase 7 caught a real layout bug: cs-aeo.md placed
at `marketing-skill/agents/cs-aeo.md` and `marketing-skill/commands/
cs-aeo.md` was unreachable by `scripts/generate-docs.py` (which only
walks root `agents/<domain>/` and root `commands/`). Result: docs/
pages for cs-aeo agent + /cs:aeo command were never generated.

**Moved to repo-canonical locations:**
- `marketing-skill/agents/cs-aeo.md` → `agents/marketing/cs-aeo.md`
- `marketing-skill/commands/cs-aeo.md` → `commands/cs-aeo.md`

Cleaned empty `marketing-skill/agents/` + `marketing-skill/commands/`
directories. Re-ran `scripts/generate-docs.py`: 401 → 403 pages
(73 agents + 34 commands — both new entries present).

## CHANGELOG.md

Added [2.7.3] - 2026-05-17 entry with full Added / Changed / Layout
fix / Cross-platform sync / Honest audit results / PRs / Verification
sections. Audit results documented verbatim including the known
false-positives — no claims of clean security where the auditor flagged
patterns it can't disambiguate.

https://claude.ai/code/session_01FEUmeuYhmnxVFq7EZM8ZSw
 2026-05-17 07:44:02 +00:00
Alireza Rezvani
9dd6fd184c
feat(slo-architect): Phase 4 — SLO/SLI/error-budget discipline (#605) 
Phase 4 of the multi-skill build effort. Same 14-step pipeline.

## What landed

### New skill: engineering/slo-architect

End-to-end SLO discipline per Google SRE Workbook. Published as BOTH:
- Standalone plugin: engineering/slo-architect/
- Bundled mirror:    engineering/skills/slo-architect/

3 stdlib-only Python tools (Karpathy complexity 95/100):
- slo_designer.py             — generates SLO definitions; refuses to render
                                 if required fields missing (owner, policy doc,
                                 SLI numerator/denominator). Supports 5 SLI
                                 types: request-success-rate, request-latency,
                                 availability-time, data-freshness, correctness.
- error_budget_calculator.py  — computes error budget AND the canonical
                                 multi-window burn-rate alert thresholds:
                                 fast (1h/5m, page), slow (6h/30m, page),
                                 ticket (3d/6h). Output is PromQL-shaped,
                                 ready to paste into Prometheus rules.
- slo_review.py               — audits SLO docs for 7 common bugs:
                                 target ≥99.99, target ≤99, window <7d,
                                 window >90d, no SLI definition, no error
                                 budget policy, CPU-as-SLI.

4 reference docs:
- slo_principles.md   — SLI vs SLO vs SLA, Google SRE Workbook canon
- sli_design.md       — 5 SLI types with examples and anti-patterns
- error_budget.md     — error budget math, burn-rate alerts, budget policy
- composition.md      — how SLOs feed feature-flags, chaos, kubernetes-operator

Asset templates:
- slo_template.yaml          — fillable SLO YAML with all required fields
- error_budget_policy.md     — fillable 4-state policy (HEALTHY / CAUTION /
                                CRITICAL / VIOLATED)

Plus: SKILL.md, README.md, /slo-design slash command.

## Composition with prior phases

Explicit wire-up to the rest of the portfolio:
- feature-flags-architect.kill_switch_audit references SLO burn-rate
- chaos-engineering.blast_radius_calculator takes SLO error budget as input
- kubernetes-operator capability level L4 requires SLOs + Prometheus rules

The SLO is the unifying number: rollout abort, chaos blast radius, and
operator capability all reference it. references/composition.md walks
through end-to-end use.

## Audit verdict (evidence-based)

Closest existing skill: engineering/observability-designer covers SLI/SLO as
ONE topic among many (metrics, logs, traces, dashboards, alerting). It has
no dedicated tools and is breadth-not-depth. slo-architect is the focused
SLO discipline with deterministic Python tools — same gap pattern as
kubernetes-operator vs senior-devops.

## Marketplace / registry

- marketplace.json: slo-architect registered as standalone plugin
- engineering-advanced-skills bundle: 49 → 50 skills, version → 2.4.4
- engineering/.claude-plugin/plugin.json: version + skill list updated
- mkdocs.yml: nav entry under "Engineering - POWERFUL"
- docs/skills/engineering/slo-architect.md: docs page (manual)
- docs/commands/slo-design.md: auto-generated
- .codex/, .gemini/: synced

## Karpathy-coder gates

- complexity_checker (strict): 95/100 average — same top score as
  chaos-engineering. 1 WARN (depth 7 in slo_review.py from generator
  expressions). Verdict: WARN, not FAIL.
- All 1689 tests pass (was 1671; +18 for the new skill).
- mkdocs build --strict: succeeded in 12.47s.

## Verifiable success criteria (all green)

✓  scripts/*.py --help     → exit 0 for all 3 scripts
✓  SKILL.md frontmatter    → name + description + tags + compatible_tools
✓  plugin.json schema      → 8 fields exact (verified)
✓  sync_skill_bundles      → standalone ↔ bundled mirror in sync
✓  marketplace.json        → standalone entry + bundle counts updated
✓  generate-docs.py        → command page generated (skill page manual)
✓  mkdocs build --strict   → succeeded
✓  cross-tool sync         → codex + gemini synced
✓  pytest tests/           → 1689 passed, 0 failed
✓  CHANGELOG.md            → [Unreleased] entry expanded for Phase 4
✓  Self-test               → error_budget_calculator on 99.9% / 28d emits
                             correct burn-rate (14.4 fast, 6 slow, 1 ticket)
✓  Composition             → references named skills explicitly compose

## Phase 1+2+3+4 cumulative

- 4 new skills: feature-flags-architect, kubernetes-operator,
                chaos-engineering, slo-architect
- 12 new Python tools (all stdlib, all <250 LOC, average complexity 92/100)
- 16 new reference docs
- 4 new slash commands (/flag-cleanup, /operator-audit, /chaos-experiment,
                        /slo-design)

https://claude.ai/code/session_01Dq12xJakFRxwaoU8Pqejdm

Co-authored-by: Claude <noreply@anthropic.com>
 2026-05-10 07:39:05 +02:00
Claude
23eefc2e9a
feat(skills): ship chaos-engineering (Phase 3 — resilience testing discipline) 
Phase 3 of the multi-skill build effort. Same 14-step pipeline. Composes
explicitly with feature-flags-architect (kill switches as abort triggers)
and kubernetes-operator (operators are common chaos targets).

## What landed

### New skill: engineering/chaos-engineering

End-to-end chaos engineering discipline. Published as BOTH:
- Standalone plugin: engineering/chaos-engineering/
- Bundled mirror:    engineering/skills/chaos-engineering/

3 stdlib-only Python tools (Karpathy complexity 95/100 — best in portfolio):
- experiment_designer.py        — generates structured plans with hypothesis,
                                   steady-state, blast radius, abort criteria,
                                   rollback. Refuses to render plans without
                                   abort criteria (exit code 1).
- blast_radius_calculator.py    — computes affected users + error budget
                                   consumption + GREEN/YELLOW/RED risk score.
                                   Validates inputs (0 ≤ traffic-share ≤ 1).
- experiment_postmortem.py      — blameless postmortems from plan + result log;
                                   detects blame-laden language ("fault of",
                                   "should have known", "stupid", etc.) and
                                   warns at write time.

4 reference docs:
- chaos_principles.md      — 4 founding principles + 5th abort principle,
                              maturity model, history, when-to-start checklist
- experiment_design.md      — 7-section plan structure, pre-flight checklist,
                              time-boxing, escalation
- attack_taxonomy.md        — 7 attack types (latency / error / resource /
                              network-partition / dependency-failure / time-skew
                              / infrastructure) with magnitudes and tooling
- tooling_landscape.md      — Chaos Toolkit / Mesh / Litmus / Gremlin / AWS FIS
                              / DIY decision tree

Templates:
- experiment_template.md    — fill-in plan with all 7 sections
- postmortem_template.md    — blameless postmortem structure

Plus: SKILL.md (213 lines), README.md, /chaos-experiment slash command.

### Audit verdict (evidence-based)

Closest existing skills:
- engineering-team/incident-response — for actual incidents, not prevention
- engineering-team/red-team — adversarial; different goal (find attack paths)
- engineering-team/threat-detection — hunting; different goal
- engineering/observability-designer — measurement, not fault injection
None cover the chaos-engineering discipline (hypothesis-driven fault injection
with bounded blast radius). Verdict: BUILD. Gap is real and tooling-shaped.

### Composition story (Phase 1+2+3 form a stack)

```
feature-flags-architect.kill_switch_audit.py
  ↓ defines kill switches that ↓
chaos-engineering.experiment_designer.py
  ↓ designs experiments against ↓
kubernetes-operator (and other targets)
```

Together: a complete progressive-delivery + resilience-testing stack.

### Marketplace / registry

- marketplace.json: chaos-engineering registered as standalone plugin
- engineering-advanced-skills bundle: 47 → 48 skills, version → 2.4.2
- engineering/.claude-plugin/plugin.json: version + skill list updated
- mkdocs.yml: nav entry under "Engineering - POWERFUL"
- docs/skills/engineering/chaos-engineering.md: docs page (manual,
  pending generate-docs.py classification fix)
- docs/commands/chaos-experiment.md: auto-generated
- .codex/, .gemini/: synced

### Karpathy-coder gates

- complexity_checker (strict): 95/100 average — BEST score in the new
  portfolio. Only 1 WARN (depth 5 in blast_radius_calculator.py validation
  branches; the other 2 scripts hit no findings whatsoever).
- All 1666 tests pass (was 1648; added 18 for the new skill).
- mkdocs build --strict: succeeded in 13.33s.

### Verifiable success criteria (all green)

✓  scripts/*.py --help     → exit 0 for all 3 scripts
✓  SKILL.md frontmatter    → name + description + tags + compatible_tools
✓  plugin.json schema      → 8 fields exact (verified by check_plugin_json.py)
✓  sync_skill_bundles      → standalone ↔ bundled mirror in sync
✓  marketplace.json        → standalone entry + bundle counts updated
✓  generate-docs.py        → command page generated (skill page manual)
✓  mkdocs build --strict   → succeeded
✓  cross-tool sync         → codex + gemini synced
✓  pytest tests/           → 1666 passed, 0 failed
✓  CHANGELOG.md            → [Unreleased] entry expanded for Phase 3
✓  Self-test (RED case)    → 50% blast radius on 99.9% baseline correctly
                             classifies as RED (17.33% of monthly budget) and
                             returns ABORT recommendation
✓  Composition test        → references named skills explicitly compose

## Phase 1+2+3 cumulative

- 3 new skills: feature-flags-architect, kubernetes-operator, chaos-engineering
- 9 new Python tools (all stdlib, all <200 LOC, average complexity 90/100)
- 12 new reference docs (~250-500 lines each)
- 3 new slash commands (/flag-cleanup, /operator-audit, /chaos-experiment)
- 2 repo-infrastructure scripts (sync_skill_bundles, check_plugin_json)
- 1 pre-existing test fix (full-page-screenshot CI red)

## Files

- engineering/chaos-engineering/                                (new standalone plugin)
- engineering/skills/chaos-engineering/                         (new bundled mirror)
- commands/chaos-experiment.md                                  (new slash command)
- docs/skills/engineering/chaos-engineering.md                  (new docs page)
- docs/commands/chaos-experiment.md                             (auto-generated)
- mkdocs.yml                                                    (nav entries)
- .claude-plugin/marketplace.json                               (registered)
- engineering/.claude-plugin/plugin.json                        (bundle bumped)
- CHANGELOG.md                                                  ([Unreleased] expanded)
- .codex/, .gemini/                                             (cross-tool sync)

https://claude.ai/code/session_01Dq12xJakFRxwaoU8Pqejdm
 2026-05-09 21:24:16 +00:00
Claude
6c16309801
feat(skills): ship kubernetes-operator (Phase 2 — operator pattern discipline) 
Phase 2 of the multi-skill build effort. Same 14-step pipeline as Phase 1.

## What landed

### New skill: engineering/kubernetes-operator

End-to-end Kubernetes Operator discipline. Published as BOTH:
- Standalone plugin: engineering/kubernetes-operator/
- Bundled mirror:    engineering/skills/kubernetes-operator/

3 stdlib-only Python tools:
- crd_validator.py            — checks CRD YAMLs for status subresource,
                                 structural schema, conditions array, printer
                                 columns, version policy, scope
- reconcile_lint.py            — finds reconcile-loop bugs in Go: time.Sleep,
                                 spec mutation via r.Update, missing requeue,
                                 oversized reconcile bodies, panic/os.Exit,
                                 unbalanced finalizer add/remove
- operator_capability_audit.py — scores against OperatorHub Capability
                                 Levels 1-5 with concrete next-level steps

4 reference docs:
- operator_pattern.md   — what an operator IS, when to use vs Helm/Deployment
- crd_design.md         — anatomy of a production CRD, versioning, conversion
- reconcile_loop.md     — idempotence patterns, error/requeue, status subresource
- tooling_landscape.md  — controller-runtime / kubebuilder / operator-sdk /
                          metacontroller / KOPF / java-operator-sdk decision tree

Asset templates:
- crd_template.yaml       — passes crd_validator.py PASS-clean
- reconcile_skeleton.go   — passes reconcile_lint.py PASS-clean

Plus: SKILL.md (213 lines), README.md, /operator-audit slash command.

### Audit verdict (evidence-based)

Closest existing coverage:
- engineering-team/senior-devops — kubectl / blue-green deploys, no operators
- engineering/helm-chart-builder — Helm charts (different abstraction)
- engineering-team/cloud-security — k8s RBAC at high level
None cover the Operator pattern (CRD + controller + reconcile loop).
Verdict: BUILD. Gap is real and tooling-shaped.

### Self-test (meta-validation)

During build, the new linters caught 4 real bugs in their own asset templates:
- crd_validator.py wrongly anchored regexes to start-of-line, misclassifying
  indented YAML keys (scope, singular, listKind) as missing
- reconcile_lint.py checked finalizer add/remove balance per-function,
  missing the cross-function pattern in the asset (Add in main reconcile,
  Remove in reconcileDelete)
Both linters fixed; assets re-tested; both PASS clean.

This is Karpathy principle 4 in action: verifiable goals catch real bugs.

### Marketplace / registry

- marketplace.json: kubernetes-operator registered as standalone plugin
- engineering-advanced-skills bundle: 45 → 46 → 47 skills, version → 2.4.1
- engineering/.claude-plugin/plugin.json: version + skill list updated
- mkdocs.yml: nav entry under "Engineering - POWERFUL"
- docs/skills/engineering/kubernetes-operator.md: docs page (manual,
  pending generate-docs.py classification fix)
- docs/commands/operator-audit.md: auto-generated
- .codex/, .gemini/: synced

### Karpathy-coder gates

- complexity_checker (strict): 85/100 average, depth-4-to-6 WARNs (lambdas
  in capability audit). Same range as karpathy-coder's own scripts (70/100
  baseline). Verdict: WARN, not FAIL.
- All 1648 tests pass (was 1630; added 18 for the new skill).
- mkdocs build --strict: succeeded in 14.44s.

### Verifiable success criteria (all green)

✓  scripts/*.py --help     → exit 0 for all 3 scripts
✓  SKILL.md frontmatter    → name + description + tags + compatible_tools
✓  plugin.json schema      → 8 fields exact (verified by check_plugin_json.py)
✓  sync_skill_bundles      → standalone ↔ bundled mirror in sync
✓  marketplace.json        → standalone entry + bundle counts updated
✓  generate-docs.py        → command page generated (skill page manual)
✓  mkdocs build --strict   → succeeded
✓  cross-tool sync         → codex + gemini synced
✓  pytest tests/           → 1648 passed, 0 failed
✓  CHANGELOG.md            → [Unreleased] entry expanded
✓  Self-test               → linters caught + fixed 4 real bugs in own assets

## Files

- engineering/kubernetes-operator/                              (new standalone plugin)
- engineering/skills/kubernetes-operator/                       (new bundled mirror)
- commands/operator-audit.md                                    (new slash command)
- docs/skills/engineering/kubernetes-operator.md                (new docs page)
- docs/commands/operator-audit.md                               (auto-generated)
- mkdocs.yml                                                    (nav entries)
- .claude-plugin/marketplace.json                               (registered)
- engineering/.claude-plugin/plugin.json                        (bundle bumped)
- CHANGELOG.md                                                  ([Unreleased] expanded)
- .codex/, .gemini/                                             (cross-tool sync)

https://claude.ai/code/session_01Dq12xJakFRxwaoU8Pqejdm
 2026-05-09 09:01:45 +00:00
Claude
0c7d19d297
feat(skills): ship feature-flags-architect (Phase 1 pilot — dual-publish) 
Phase 1 of the multi-skill build effort. Ships the first new skill end-to-end
through the 14-step pipeline: scoped, audited, built, gated, mirrored, doc'd,
and registered.

## What landed

### New skill: engineering/feature-flags-architect

End-to-end feature-flag discipline. Published as BOTH:
- Standalone plugin: engineering/feature-flags-architect/
- Bundled mirror:    engineering/skills/feature-flags-architect/

3 stdlib-only Python tools:
- flag_debt_scanner.py — finds stale flags via git log -S + age heuristic
- rollout_planner.py   — generates ring/linear/log/cohort phased schedule
- kill_switch_audit.py — verifies every flag has documented kill switch

4 reference docs:
- flag_taxonomy.md       — 4 types decision tree (Release/Experiment/Operational/Permission)
- provider_comparison.md — LaunchDarkly/GrowthBook/Statsig/Unleash/Flipt/DIY trade-offs
- rollout_strategies.md  — strategies, abort criteria, hold-time rules
- flag_lifecycle.md      — 6-phase lifecycle (request → archive) with SLAs + worked example

Plus: SKILL.md (213 lines), README.md, asset template, /flag-cleanup slash command.

### Audit verdict (evidence-based)

Closest existing skill: engineering/skills/release-manager (~30 lines on flags;
documents 4 types + Python integration example). marketing-skill/ab-test-setup
references flags only in tooling list. Neither provides debt scanner, rollout
planner, or kill-switch audit. Verdict: BUILD. Gap is real and tooling-shaped.

### Marketplace / registry

- marketplace.json: feature-flags-architect registered as standalone plugin
- engineering-advanced-skills bundle: 44 → 45 skills, version 2.3.3 → 2.4.0
- engineering/.claude-plugin/plugin.json: version bumped + skill listed
- mkdocs.yml: nav entry under "Engineering - POWERFUL"
- docs/skills/engineering/feature-flags-architect.md: docs page (manual,
  generate-docs.py has a pre-existing classification bug fixing top-level
  vs sub-skill detection — out of scope this turn)
- docs/commands/flag-cleanup.md: auto-generated by generate-docs.py
- .codex/skills/feature-flags-architect: symlink created
- .gemini/skills/feature-flags-architect: synced

### Karpathy-coder gates (per user directive: block on FAIL)

- complexity_checker (strict): 90/100 average (1 WARN per script on nesting
  depth — same intrinsic pattern as canonical karpathy-coder tools, which
  themselves score 70/100 strict). Verdict: WARN, not FAIL.
- diff_surgeon: NOISY (whitespace + docstrings flagged on new files —
  intrinsic false-positive for greenfield code; karpathy-coder's own scripts
  hit the same noise pattern).
- goal_verifier: same MISSING verdict as the flagship llm-wiki SKILL.md;
  literal `→ verify:` syntax not used (would harm readability).
- All 1630 tests pass (was 1629; added 12 smoke + 6 integrity for the new skill).

### Verifiable success criteria (all green)

✓  scripts/*.py --help     → exit 0 for all 3 scripts
✓  SKILL.md frontmatter    → name + description + tags + compatible_tools
✓  plugin.json schema      → 8 fields exact (verified by check_plugin_json.py)
✓  sync_skill_bundles --check engineering/feature-flags-architect → exit 0
✓  marketplace.json        → standalone entry + bundle version bumped
✓  generate-docs.py        → command page generated (skill page manual)
✓  mkdocs build --strict   → succeeded in 14.81s
✓  cross-tool sync         → codex + gemini synced
✓  pytest tests/           → 1630 passed, 0 failed
✓  CHANGELOG.md            → [Unreleased] entry added
✓  False-positive purge    → removed FLAG_X regex pattern from scanner after
                             it matched my own FLAG_PATTERNS constant

## Files

- engineering/feature-flags-architect/                          (new standalone plugin)
- engineering/skills/feature-flags-architect/                   (new bundled mirror)
- commands/flag-cleanup.md                                      (new slash command)
- docs/skills/engineering/feature-flags-architect.md            (new docs page)
- docs/commands/flag-cleanup.md                                 (auto-generated)
- mkdocs.yml                                                    (nav entries)
- .claude-plugin/marketplace.json                               (registered)
- engineering/.claude-plugin/plugin.json                        (bundle bumped)
- CHANGELOG.md                                                  ([Unreleased] entry)
- .codex/, .gemini/                                             (cross-tool sync)

https://claude.ai/code/session_01Dq12xJakFRxwaoU8Pqejdm
 2026-05-09 06:10:43 +00:00
Reza Rezvani
9c2facebf4 fix(karpathy-coder): pass 8-phase plugin audit + wire repo integration 
Auto-fixes from plugin-audit pipeline:

Phase 2 (70.4 → 75.0 GOOD):
- Added README.md with quick start, tool descriptions, enforcement levels

Phase 3 (51.7 → 63.5, above 60):
- Added expected_outputs/ with 4 JSON fixtures (one per tool)
- Completeness 66.7 → 85.0

Phase 6 (marketplace + agent + command):
- Added karpathy-coder to .claude-plugin/marketplace.json (category: development)
- Mirrored cs-karpathy-reviewer to agents/engineering/
- Mirrored /karpathy-check to commands/
- mkdocs.yml: added skill + command nav entries

Phase 7 (ecosystem sync):
- Ran sync-codex-skills.py + sync-gemini-skills.py
- karpathy-coder now in both indexes

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-04-12 13:34:55 +02:00
Reza Rezvani
8c480b86bd merge: dev into feature/llm-wiki-plugin — resolve skill count conflicts 
# Conflicts:
#	.claude-plugin/marketplace.json
#	.codex/skills-index.json
#	.gemini/skills-index.json
#	CLAUDE.md
 2026-04-11 01:52:15 +02:00
Reza Rezvani
b6ca45ddec feat(engineering): add llm-wiki plugin — second brain for Claude Code + Obsidian 
Implements Karpathy's LLM Wiki pattern as a production-grade plugin. The LLM
incrementally ingests sources into a persistent, interlinked Obsidian vault —
updating entity/concept/source pages, flagging contradictions, maintaining an
index and append-only log. Knowledge compounds instead of being re-derived by
RAG on every query.

Plugin contents (engineering/llm-wiki/):
- SKILL.md with `context: fork` frontmatter for skill chaining
- 3 sub-agents: wiki-ingestor, wiki-librarian, wiki-linter
- 5 slash commands: /wiki-init, /wiki-ingest, /wiki-query, /wiki-lint, /wiki-log
- 8 Python tools (stdlib only): init_vault, ingest_source, update_index,
  append_log, wiki_search (BM25), lint_wiki, graph_analyzer, export_marp
- 8 reference docs: schema, page-formats, ingest/query/lint workflows,
  obsidian-setup, cross-tool-setup, memex-principles
- Vault templates: CLAUDE.md, AGENTS.md, .cursorrules, index.md, log.md,
  5 page templates (entity, concept, source, comparison, synthesis)
- Worked example vault on "LLM interpretability"
- .claude-plugin/plugin.json manifest

Cross-tool compatibility: the scripts are pure Python stdlib. Only the schema
loader changes per tool (CLAUDE.md for Claude Code, AGENTS.md for Codex CLI /
Cursor / Antigravity / OpenCode / Gemini CLI, .cursorrules for legacy Cursor).
init_vault.py --tool all installs all three.

Repo-level registration:
- Commands mirrored to top-level commands/ for repo-wide discovery
- Agents mirrored to agents/engineering/ as cs-wiki-{ingestor,librarian,linter}
- .claude-plugin/marketplace.json: new llm-wiki entry + version bump to v2.3.0
- CLAUDE.md updated: 234 skills, 313 Python tools, 432 refs, 28 agents, 27 commands

Also saved (deferred): craighewitt-mattpocock reimplementation plan at
documentation/implementation/ — 4-pod proposal for building better versions
of selected skills from thecraighewitt-skills and mattpocock-skills
collections. Not executed; awaiting user confirmation on scope.

End-to-end smoke test passed: init_vault → ingest → update_index → append_log
→ wiki_search → lint → graph_analyzer → export_marp all run against a fresh
vault with real pages, wikilinks, and frontmatter.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-04-11 01:14:11 +02:00
Elkidogz
2d1f0d2b53 feat(engineering): add tc-tracker skill 
Self-contained skill for tracking technical changes with structured JSON
records, an enforced state machine, and a session handoff format that lets
a new AI session resume work cleanly when a previous one expires.

Includes:
- 5 stdlib-only Python scripts (init, create, update, status, validator)
  all supporting --help and --json
- 3 reference docs (lifecycle state machine, JSON schema, handoff format)
- /tc dispatcher in commands/tc.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-04-08 15:07:03 -04:00
Reza Rezvani
ce1d7925cc feat(engineering): integrate focused-fix skill — docs, command, agent, marketplace 
- Normalize SKILL.md frontmatter to repo standard (remove non-standard
  license, metadata.* fields; inline description)
- Generate docs page (docs/skills/engineering/focused-fix.md)
- Add to mkdocs.yml nav (skills + commands)
- Create /focused-fix slash command (commands/ + .claude/commands/)
- Add to cs-senior-engineer agent (skill integration + new workflow #4)
- Update marketplace.json and plugin.json descriptions (30 → 31 skills)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-23 13:59:30 +01:00
Reza Rezvani
90cef3b3ac feat(commands): add /seo-auditor — 7-phase SEO audit pipeline for documentation 
- 7 phases: discovery → meta tags → content quality → keywords → links → sitemap → report
- Integrates 8 marketing-skill scripts: seo_checker, content_scorer,
  humanizer_scorer, headline_scorer, seo_optimizer, sitemap_analyzer,
  schema_validator, topic_cluster_mapper
- References 6 SEO knowledge bases for audit framework, AI search,
  content optimization, URL design, internal linking, AI detection
- Auto-fixes: generic titles, missing descriptions, broken links, orphan pages
- Preserves high-ranking pages — only fixes critical issues on those
- Registered in both commands/ (distributable) and .claude/commands/ (local)

Also: sync all doc counts — 28 plugins, 26 eng-core skills, 21 commands

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-18 10:28:17 +01:00
Alireza Rezvani
920dc12a74
feat(engineering-team): add a11y-audit skill — WCAG 2.2 accessibility audit & fix (#376) 
Built from scratch (replaces reverted PR #375 contribution).

Skill package:
- SKILL.md: 1132 lines, 3-phase workflow (scan → fix → verify),
  per-framework fix patterns (React, Next.js, Vue, Angular, Svelte, HTML),
  CI/CD integration guide, 20+ issue type coverage
- scripts/a11y_scanner.py: static scanner detecting 20+ violation types
  across HTML/JSX/TSX/Vue/Svelte/CSS — severity-ranked, CI-friendly exit codes
- scripts/contrast_checker.py: WCAG contrast calculator with AA/AAA checks,
  --suggest mode, --batch CSS scanning, named color support
- references/wcag-quick-ref.md: WCAG 2.2 Level A/AA criteria table
- references/aria-patterns.md: ARIA roles, live regions, keyboard interaction
- references/framework-a11y-patterns.md: React, Vue, Angular, Svelte fix patterns
- assets/sample-component.tsx: sample file with intentional violations
- expected_outputs/: scan report, contrast output, JSON output samples
- /a11y-audit slash command, settings.json, plugin.json, README.md

Validation: 97.6/100 (EXCELLENT), quality 73.9/100 (B-), scripts 2/2 PASS

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-18 08:42:20 +01:00
Reza Rezvani
920e8547af feat(commands): add /plugin-audit — 8-phase validation pipeline for skills and plugins 
- Add commands/plugin-audit.md (distributable) + .claude/commands/plugin-audit.md (local invocation)
- 8 phases: discovery, structure validation, quality scoring, script testing,
  security audit, marketplace compliance, ecosystem integration, domain code review
- Auto-fixes non-critical issues, only prompts user for breaking changes
- Integrates skill_validator.py, quality_scorer.py, script_tester.py, skill_security_auditor.py
- Domain-appropriate review via cs-* agents (engineering, product, marketing, etc.)
- Update product-team counts: 12→14 skills, 13→16 tools, 7→8 commands
- Add /code-to-prd and /plugin-audit to mkdocs.yml nav
- Regenerate docs (248 pages, 19 commands)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-17 15:38:00 +01:00
Reza Rezvani
4b7a084ee3 feat(code-to-prd): expand to fullstack — add NestJS, Django, Express, FastAPI support 
- Rename frontend_analyzer.py → codebase_analyzer.py — now detects backend
  frameworks via package.json (NestJS, Express, Fastify) and project files
  (manage.py, requirements.txt for Django, FastAPI, Flask)
- Add backend route extraction: NestJS @Controller/@Get decorators,
  Django urls.py path() patterns
- Add model/entity extraction: Django models.Model fields, NestJS @Entity
  and DTO classes
- Add stack_type detection (frontend / backend / fullstack) to analysis output
- SKILL.md: add Supported Stacks table, backend directory guide, backend
  endpoint inventory template, backend page type strategies, backend pitfalls
- references/framework-patterns.md: add NestJS, Express, Django, DRF, FastAPI
  pattern tables + database model patterns + backend validation patterns
- references/prd-quality-checklist.md: add backend-specific checks (endpoints,
  DTOs, models, admin, middleware, migrations)
- Update all descriptions and keywords across plugin.json, settings.json,
  marketplace.json, and /code-to-prd command

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-17 12:28:30 +01:00
Reza Rezvani
70ada54c95 feat(code-to-prd): add ecosystem integration — command, settings, marketplace 
- Fix plugin.json version: 1.0.0 → 2.1.2 (repo versioning)
- Add /code-to-prd slash command (4-step workflow: analyze → scaffold → fill → finalize)
- Add settings.json with command registration and platform metadata
- Add code-to-prd entry to marketplace.json with keywords and category

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-17 12:20:16 +01:00
Leo
7857cff3bd feat: add product slash commands 2026-03-11 14:58:51 +01:00
Reza Rezvani
4e9f1d934d feat(engineering): add google-workspace-cli skill with 5 Python tools 
New skill for Google Workspace administration via the gws CLI:
- SKILL.md with 4 workflows (Gmail, Drive/Sheets, Calendar, Security Audit)
- 5 stdlib-only Python scripts (doctor, auth setup, recipe runner, audit, analyzer)
- 3 reference docs, 2 asset files, 43 built-in recipes, 10 persona bundles
- cs-workspace-admin agent, /google-workspace slash command
- Standalone marketplace plugin entry with .claude-plugin/plugin.json
- Cross-platform sync (Codex CLI, Gemini CLI), MkDocs docs pages
- All documentation updated (173 skills, 250 tools, 15 agents, 15 commands)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-11 09:59:40 +01:00
Reza Rezvani
cb3fa6b7ea feat: integrate saas-metrics-coach, add finance commands, remove seek-and-analyze-video 
- Integrate saas-metrics-coach into cs-financial-analyst agent with SaaS health
  and unit economics workflows
- Add /financial-health and /saas-health slash commands
- Add /update-docs repo command for post-creation sync pipeline
- Remove seek-and-analyze-video skill (requires paid external API)
- Update all documentation (CLAUDE.md, README.md, docs site, marketplace)
- Sync Codex CLI (150 skills), Gemini CLI (207 items), fix count consistency
- Regenerate 206 MkDocs pages, fix docs/index.md meta 170→171,
  getting-started.md finance bundle 1→2

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-10 14:29:41 +01:00
Reza Rezvani
5add886197 fix: repair 25 Python scripts failing --help across all domains 
- Fix Python 3.10+ syntax (float | None → Optional[float]) in 2 scripts
- Add argparse CLI handling to 9 marketing scripts using raw sys.argv
- Fix 10 scripts crashing at module level (wrap in __main__, add argparse)
- Make yaml/prefect/mcp imports conditional with stdlib fallbacks (4 scripts)
- Fix f-string backslash syntax in project_bootstrapper.py
- Fix -h flag conflict in pr_analyzer.py
- Fix tech-debt.md description (score → prioritize)

All 237 scripts now pass python3 --help verification.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-10 05:51:27 +01:00
Reza Rezvani
670a1a61f3 fix: audit and repair all plugins, agents, and commands 
- Fix 12 command files: correct CLI arg syntax, script paths, and usage docs
- Fix 3 agents with broken script/reference paths (cs-content-creator,
  cs-demand-gen-specialist, cs-financial-analyst)
- Add complete YAML frontmatter to 5 agents (cs-growth-strategist,
  cs-engineering-lead, cs-senior-engineer, cs-financial-analyst,
  cs-quality-regulatory)
- Fix cs-ceo-advisor related agent path
- Update marketplace.json metadata counts (224 tools, 341 refs, 14 agents,
  12 commands)

Verified: all 19 scripts pass --help, all 14 agent paths resolve, mkdocs
builds clean.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-10 01:17:31 +01:00
Reza Rezvani
67f3922e4f feat(product,pm): world-class product & PM skills audit — 6 scripts, 5 agents, 7 commands, 23 references/assets 
Phase 1 — Agent & Command Foundation:
- Rewrite cs-project-manager agent (55→515 lines, 4 workflows, 6 skill integrations)
- Expand cs-product-manager agent (408→684 lines, orchestrates all 8 product skills)
- Add 7 slash commands: /rice, /okr, /persona, /user-story, /sprint-health, /project-health, /retro

Phase 2 — Script Gap Closure (2,779 lines):
- jira-expert: jql_query_builder.py (22 patterns), workflow_validator.py
- confluence-expert: space_structure_generator.py, content_audit_analyzer.py
- atlassian-admin: permission_audit_tool.py
- atlassian-templates: template_scaffolder.py (Confluence XHTML generation)

Phase 3 — Reference & Asset Enrichment:
- 9 product references (competitive-teardown, landing-page-generator, saas-scaffolder)
- 6 PM references (confluence-expert, atlassian-admin, atlassian-templates)
- 7 product assets (templates for PRD, RICE, sprint, stories, OKR, research, design system)
- 1 PM asset (permission_scheme_template.json)

Phase 4 — New Agents:
- cs-agile-product-owner, cs-product-strategist, cs-ux-researcher

Phase 5 — Integration & Polish:
- Related Skills cross-references in 8 SKILL.md files
- Updated product-team/CLAUDE.md (5→8 skills, 6→9 tools, 4 agents, 5 commands)
- Updated project-management/CLAUDE.md (0→12 scripts, 3 commands)
- Regenerated docs site (177 pages), updated homepage and getting-started

Quality audit: 31 files reviewed, 29 PASS, 2 fixed (copy-frameworks.md, governance-framework.md)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-03-10 01:08:45 +01:00
Alireza Rezvani
fa07912835
feat: add 6 agents + 5 slash commands for full coverage (v2.7.0) (#293) 
Phase 3: 6 new agents (all 9 categories covered) + 5 slash commands.
 2026-03-07 12:36:03 +01:00
Reza Rezvani
e8af39aed6 feat(foundation): create directory structure and standards library 
- Create root-level directories: agents/, commands/, standards/, templates/
- Port 5 core standards from global Claude standards
- Adapt standards for claude-skills context (cs-* prefix, Python tools, skills)
- Create sprint planning documents (context.md, plan.md)
- All directories tracked with .gitkeep files

Standards created:
- communication-standards.md (absolute honesty, zero fluff, pragmatic focus)
- quality-standards.md (Python tool quality, agent workflows, testing)
- git-workflow-standards.md (conventional commits, semantic versioning)
- documentation-standards.md (Markdown standards, living docs, templates)
- security-standards.md (secret detection, dependency security, input validation)

Sprint plan ready for Days 1-6 implementation.

Phase: 1 (Foundation)
Issues: #8, #9
 2025-11-05 11:37:53 +01:00