cc-codeconductor 1.1.0 → 1.3.0

package/presets/agy/skills/openspec/SKILL.md

@@ -1,36 +1,66 @@
 ---
 name: openspec
 description:
-  OpenSpec backlog format, state machine, and delivery workflow for CodeConductor.
-  Use when running /cc-openspec or delivering a BACKLOG.md item.
-  To create or append BACKLOG.md, use /cc-backlog (skill backlog).
+  Guides agents through OpenSpec delivery from BACKLOG.md (validate, analyze,
+  test-before-implement, scorecard, archive). Use when running /cc-openspec,
+  /cc:openspec, or delivering an existing backlog item. Authoring BACKLOG.md
+  is skill backlog, not this skill.
 ---
 
-# OpenSpec / BACKLOG Skill
+# OpenSpec delivery
 
-Authoring (create or append `BACKLOG.md`, then `openspec validate` / `plan`) is
-`/cc-backlog` and skill `backlog`. This skill is **delivery**.
+## Overview
 
-## BACKLOG.md contract
+This skill delivers an existing `BACKLOG.md` item. It is a workflow with CLI
+gates, not a reference doc. Specs describe WHAT; `design.md` describes HOW.
 
-`BACKLOG.md` at repo root is the operational queue. Required sections:
+## When to Use
 
-- `## Global` — Product, Strategy, Policy, Review required, TDD required
-- `## Items` — active backlog entries
-- `## Archive` — completed entries (do not re-execute)
+- `/cc-openspec` or `openspec next` / `plan` / `done` / `archive`
+- An item is `READY` or later and must move through the state machine
 
-Each item: `### BC-001 | Short title` with Priority (P0–P3), Status, Type, Depends on, Description, Scope, Out of scope, Acceptance (measurable checklist).
+**NOT** for creating `BACKLOG.md` (use skill `backlog`) or for stack-specific
+coding rules.
 
-## Status machine
+## Process
 
-`TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW` → `DONE` → Archive
+Local CLI is `bun run dev`. Published package is `npx cc-codeconductor`.
 
-## CLI
+1. `openspec validate` — must pass before delivery.
+2. `openspec plan BC-xxx` if the item is not yet `PLANNED`.
+3. `openspec analyze --output json` — CRITICAL findings exit 1. Do not implement.
+4. Phases: discover (`repo-explorer`) → design (`architect`) → test (`tester`) →
+   implement (`implementer`) → review (`reviewer`). If Global `TDD required: yes`,
+   test runs before implement.
+5. `openspec done` on test/implement requires `captureTddSuiteEvidence`. Handmade
+   evidence JSON is rejected.
+6. `scorecard create --task BC-xxx --from-diff` then record a verdict.
+7. `openspec archive` only after human review when `Review required: yes` and
+   the scorecard is PASS.
 
-`openspec validate | scan | plan | status | next`
+Status machine: `TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW` → `DONE`
+→ Archive. `BLOCKED` returns to `READY`. Reviewer rejection: `REVIEW` →
+`IN_PROGRESS`.
 
-## Agent phases
+## Common Rationalizations
 
-discover → repo-explorer, design → architect, test → tester, implement → implementer, review → reviewer.
+| Rationalization | Reality |
+| --- | --- |
+| Validate is bureaucracy | `openspec validate` is the gate. Skipping it is a defect. |
+| I'll add tests after green | Global TDD required means tester before implementer. |
+| I'll write the evidence JSON myself | Handmade TDD JSON is rejected. Use the verification runner. |
+| The item is small; skip analyze | `openspec analyze` CRITICAL still stops implement. |
 
-TDD required: test before implement.
+## Red Flags
+
+- Implementing while analyze reports CRITICAL
+- Archive without a PASS scorecard when review is required
+- Acceptance like "improve UX" with no measurable check
+
+## Verification
+
+- [ ] `openspec validate` exit 0
+- [ ] `openspec analyze --output json` has no CRITICAL
+- [ ] TDD evidence from the runner when TDD is required
+- [ ] `scorecard create --from-diff` recorded
+- [ ] Suite check (optional): `bun run dev scorecard suite-run --suite workflow-gates`

package/presets/agy/skills/testing-tdd/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: testing-tdd
+description:
+  Guides agents through Red-Green-Refactor with runner-captured evidence.
+  Use when running /cc-tdd-cycle, writing tests before implementation, or
+  Global TDD required is yes.
+---
+
+# Test-Driven Development
+
+## Overview
+
+Red (failing test) → Green (minimal code) → Refactor. Evidence comes from
+`captureTddSuiteEvidence`, not handmade JSON.
+
+## When to Use
+
+- `/cc-tdd-cycle`, new behavior, bug fixes, TDD-required OpenSpec items
+
+**NOT** for docs-only changes or when the Task Card forbids tests.
+
+## Process
+
+1. Write the failing test that encodes one acceptance criterion. Run the suite.
+   It MUST fail (`suiteFails === true`).
+2. Implement the minimum that turns it green. Do not expand scope.
+3. Refactor only with a green suite.
+4. Capture evidence via the verification runner (`openspec done` on test/implement
+   when TDD is required).
+5. Cover happy path, edge, and error for each behavior.
+
+Local: `bun run dev`. Pyramid default: many unit, fewer integration, rare E2E.
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+| --- | --- |
+| I'll add tests later | Later means never. Red first. |
+| This is too small to test | If it can break, it needs a failing test first. |
+| I'll write the evidence JSON | Handmade TDD JSON is rejected. |
+
+## Red Flags
+
+- Tests that assert implementation details instead of behavior
+- Green without a recorded red
+- Skipping error cases
+
+## Verification
+
+- [ ] Suite failed before implement
+- [ ] Suite passed after implement
+- [ ] Runner evidence exists (not handmade)
+- [ ] Optional: `bun run dev scorecard suite-run --suite workflow-gates`

package/presets/agy/skills/using-cc-skills/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: using-cc-skills
+description:
+  Maps incoming work to the CodeConductor slash command and workflow skill.
+  Use when starting a session or deciding which /cc-* command applies.
+---
+
+# Using CodeConductor skills
+
+## Overview
+
+Pick one slash command. Follow its skill. Invoke CLI for gates. Do not invent
+a parallel process.
+
+## When to Use
+
+- Start of a session, ambiguous request, or "which /cc should I run?"
+
+## Process
+
+| Intent | Command | Skill |
+| --- | --- | --- |
+| New backlog item | `/cc-backlog` | `backlog` |
+| Deliver a BC-xxx item | `/cc-openspec` | `openspec` |
+| New feature | `/cc-feature` | `openspec` + `testing-tdd` |
+| Bug fix | `/cc-fix` | `testing-tdd` |
+| Review a diff | `/cc-review` | `evaluation` |
+| TDD cycle only | `/cc-tdd-cycle` | `testing-tdd` |
+| Scorecard / suites | `/cc-scorecard` | `evaluation` |
+
+Then run the matching CLI (`openspec validate`, `scorecard create --from-diff`,
+`hook pre-tool`, `scorecard suite-run`).
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+| --- | --- |
+| I'll skip the slash and just code | Skipping the workflow is a defect. |
+
+## Red Flags
+
+- Two slash commands in parallel that mutate the same files
+- Implementing before `openspec analyze` when a change folder is active
+
+## Verification
+
+- [ ] One command selected and shown to the user
+- [ ] Matching skill loaded before edits

package/presets/agy/workflows/cc-api-contract.md

@@ -21,6 +21,20 @@ Command: `api-contract` (fixed for this workflow — do not infer from user text
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-api-contract`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Step 1 — Task Card validation (task-coach)
 
 Invoke `task-coach` with the request above.
@@ -81,3 +95,7 @@ or docs/OpenAPI drift.
 
 Report the final Task Card, Technical Plan, implementation summary, test report,
 review report, docs updated, compatibility impact, and residual risks.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-ask.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Recommend one CodeConductor slash command from a natural-language
+  Recommend one CodeConductor slash command from a natural-language
   problem. Does not start that workflow.
 ---
 
@@ -9,7 +9,7 @@ description: >-
 Problem: $ARGUMENTS
 
 This is a **router**, not a delivery workflow. Recommend exactly one command.
-Do **not** run the recommended `/cc:` command unless the human confirms.
+Do **not** run the recommended `/cc-` command unless the human confirms.
 
 ---
 
@@ -31,13 +31,13 @@ The catalog is only:
 
 | Slash | When |
 | ----- | ---- |
-| `/cc:feature` | new behavior |
-| `/cc:fix` | bug / regression |
-| `/cc:refactor` | structure, no behavior change |
-| `/cc:review` | inspect a diff/PR |
-| `/cc:tdd-cycle` | red → green → refactor |
-| `/cc:backlog` | create or append BACKLOG.md / objectives |
-| `/cc:openspec` | BACKLOG / BC-xxx delivery |
+| `/cc-feature` | new behavior |
+| `/cc-fix` | bug / regression |
+| `/cc-refactor` | structure, no behavior change |
+| `/cc-review` | inspect a diff/PR |
+| `/cc-tdd-cycle` | red → green → refactor |
+| `/cc-backlog` | create or append BACKLOG.md / objectives |
+| `/cc-openspec` | BACKLOG / BC-xxx delivery |
 
 If the CLI is unavailable, apply the same catalog and the same priority:
 backlog (author) vs openspec (deliver) → tdd-cycle → review → refactor → fix → feature (default).
@@ -53,4 +53,4 @@ Print:
 
 **STOP.** Wait for the human. Do not invoke the recommended workflow.
 
-For a full preset inventory (skills, commands on disk), use `/cc:help` / `cc-help`.
+For a full preset inventory (skills, commands on disk), use `/cc-help` / `cc-help`.

package/presets/agy/workflows/cc-council.md

@@ -86,3 +86,7 @@ If APPROVED (no CRITICAL findings):
 ## Completion
 
 Deliver the complete Council Verdict. The feature is only complete when tests pass and the council explicitly approves the implementation according to the specification.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc-fix` or `/cc-feature`.

package/presets/agy/workflows/cc-db-migration.md

@@ -22,6 +22,20 @@ Command: `db-migration` (fixed for this workflow — do not infer from user text
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-db-migration`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Step 1 — Task Card validation (task-coach)
 
 Invoke `task-coach` with the request above.
@@ -81,3 +95,7 @@ undocumented deployment sequencing, or model/migration drift.
 
 Report migration files changed, model files changed, tests run, lock risk, data
 risk, operational sequencing, rollback/forward-fix notes, and residual risk.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-explore.md

@@ -28,10 +28,10 @@ If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"`. Invoke `
 
 ## Step 2 — Suggest next command (orchestrator)
 
-Recommend exactly one next slash command (`/cc:feature`, `/cc:fix`, `/cc:refactor`, `/cc:review`, `/cc:backlog`, `/cc:openspec`, `/cc:triage`, …) with a one-sentence rationale. Do not start that workflow.
+Recommend exactly one next slash command (`/cc-feature`, `/cc-fix`, `/cc-refactor`, `/cc-review`, `/cc-backlog`, `/cc-openspec`, `/cc-triage`, …) with a one-sentence rationale. Do not start that workflow.
 
 ---
 
 ## Completion
 
-Report the Repo Map and the recommended next `/cc:` command.
+Report the Repo Map and the recommended next `/cc-` command.

package/presets/agy/workflows/cc-feature.md

@@ -22,6 +22,24 @@ Command: `feature` (fixed for this workflow — do not infer from user text)
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-feature`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+Skills: `using-cc-skills`, `openspec`, `testing-tdd`, `evaluation`.
+Do not skip `openspec analyze` when a change folder is active.
+"I'll add tests later" is not allowed — tester before implementer.
+
+---
+
+
 ## Step 1 — Wayfinding (repo-explorer)
 
 If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"` (and
@@ -135,3 +153,7 @@ Report the following to the human:
 
 The feature is complete only when: all tests pass, no CRITICAL review findings
 remain, and documentation reflects the implemented behavior.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-fix.md

@@ -32,6 +32,20 @@ Command: `fix` (fixed for this workflow — do not infer from user text)
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-fix`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Step 1 — Wayfinding (repo-explorer)
 
 If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"` (and
@@ -149,3 +163,7 @@ resolved.
 Report: Task Card, Implementation Summary, regression test added, Review Report
 (if applicable). The fix is complete only when: the regression test passes, the
 full suite passes, and no CRITICAL review findings remain.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-handoff.md

@@ -31,7 +31,7 @@ errors instead of pasting dumps. If unresolved credential material remains, stop
 and wait for a human (CCEP `stopOnHighRisk`).
 
 Include: goal, Task Card status (no secret fields), files touched, test
-pass/fail (not log dumps), open questions, and the next `/cc:` command.
+pass/fail (not log dumps), open questions, and the next `/cc-` command.
 
 Do not edit source or tests.
 

package/presets/agy/workflows/cc-iterative.md

@@ -22,6 +22,20 @@ Command: `iterative` (fixed for this workflow — do not infer from user text)
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-iterative`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Step 1 — Wayfinding (repo-explorer)
 
 If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"` (and

package/presets/agy/workflows/cc-openspec.md

@@ -30,6 +30,20 @@ Command: `openspec` (fixed for this workflow — do not infer from user text)
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-openspec`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Step 1 — Scan
 
 Run `npx cc-codeconductor openspec scan`. Report new, modified, and closed items.

package/presets/agy/workflows/cc-prototype.md

@@ -36,4 +36,4 @@ Invoke `implementer` in a Git worktree that is not a merge candidate. Label the
 
 ## Completion
 
-Report bounds, worktree path, and what was learned. Recommend `/cc:feature` or `/cc:fix` if the spike should become real work.
+Report bounds, worktree path, and what was learned. Recommend `/cc-feature` or `/cc-fix` if the spike should become real work.

package/presets/agy/workflows/cc-refactor.md

@@ -29,7 +29,7 @@ behavioral consequences.
 If coverage is insufficient:
 
 1. **STOP**. Report the coverage gap to the human.
-2. Suggest invoking `/cc:test-plan` first to establish coverage.
+2. Suggest invoking `/cc-test-plan` first to establish coverage.
 3. Do not proceed with the refactor until coverage is confirmed.
 
 ---
@@ -159,3 +159,7 @@ and after, Review Report (if applicable).
 The refactor is complete only when: all pre-existing tests still pass, the
 implementation matches the approved plan exactly, and no CRITICAL review
 findings remain.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-review.md

@@ -138,7 +138,7 @@ If any CRITICAL findings exist:
 - The Review Report status is **BLOCKED**
 - Report all CRITICAL findings to the human
 - Do not proceed until each CRITICAL finding is resolved
-- After resolution, invoke `/cc:review` again on the same target
+- After resolution, invoke `/cc-review` again on the same target
 
 If no CRITICAL findings exist:
 
@@ -152,3 +152,7 @@ If no CRITICAL findings exist:
 
 Deliver the complete Review Report. Never summarize or omit findings. Every
 finding must include a location and an actionable description.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc-fix` or `/cc-feature`.

package/presets/agy/workflows/cc-scorecard.md

@@ -20,6 +20,8 @@ Command: `scorecard` (fixed for this workflow — do not infer from user text)
 
 ---
 
+If a change folder exists, run `npx cc-codeconductor openspec analyze --output json` first. `--from-diff` overlays FR/SC coverage onto `acceptance` and TDD evidence onto `tests`.
+
 1. `npx cc-codeconductor scorecard create --task <id> --from-diff`
 2. Complete criteria per docs/agent-scorecard.md
 3. `scorecard regression` if needed

package/presets/agy/workflows/cc-security.md

@@ -178,3 +178,7 @@ resolved.
 Report: Task Card, Implementation Summary, regression test added, Review Report
 (if applicable). The task is complete only when: the regression test passes, the
 full suite passes, and no CRITICAL review findings remain.
+
+## Next
+
+Run `/cc-review` on the diff before merging.