cc-codeconductor 1.1.0 → 1.3.0

package/presets/codex/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/codex/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/cursor/agents/architect.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — architect v0.5.0
+# Agent Contract — architect v1.0.0
 
 ## Role
 

package/presets/cursor/agents/complexity-auditor.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — complexity-auditor v0.5.0
+# Agent Contract — complexity-auditor v1.0.0
 
 You are the Complexity Auditor — the code quality gate in the CodeConductor
 framework. You analyze diffs for bloat, unnecessary abstractions, and non-native

package/presets/cursor/agents/contract-builder.md

@@ -6,7 +6,7 @@ readonly: true
 is_background: false
 ---
 
-# Agent Contract — contract-builder v0.5.0
+# Agent Contract — contract-builder v1.0.0
 
 ## Role
 

package/presets/cursor/agents/docs.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — docs v0.5.0
+# Agent Contract — docs v1.0.0
 
 ## Role
 

package/presets/cursor/agents/goal-planner.md

@@ -6,7 +6,7 @@ readonly: true
 is_background: false
 ---
 
-# Agent Contract — goal-planner v0.5.0
+# Agent Contract — goal-planner v1.0.0
 
 ## Role
 

package/presets/cursor/agents/implementer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — implementer v0.5.0
+# Agent Contract — implementer v1.0.0
 
 ## Role
 
@@ -142,7 +142,7 @@ criteria:
 
 ---
 
-## Post-implementation evaluation (v0.5.0)
+## Post-implementation evaluation (v1.0.0)
 
 When the orchestrator invokes the Evaluation Gate, wait for scorecard verdict
 before considering the task complete. On **REVISE**, address findings and re-run

package/presets/cursor/agents/orchestrator.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — orchestrator v0.5.0
+# Agent Contract — orchestrator v1.0.0
 
 ## Role
 
@@ -255,7 +255,7 @@ routes the agents through an iterative feedback loop:
 
 ---
 
-## Evaluation Gate (v0.5.0)
+## Evaluation Gate (v1.0.0)
 
 After each agent completes a deliverable on **medium** or **high** risk tasks:
 
@@ -266,7 +266,7 @@ After each agent completes a deliverable on **medium** or **high** risk tasks:
 5. Record outcome: `npx cc-codeconductor scorecard record --task <id> --verdict PASS|REVISE|REJECT --score <n>`
 6. Route on verdict: **REVISE** → prior agent with findings; **REJECT** → `task-coach`
 
-Include `contract_version: v0.5.0` in scorecard metadata.
+Include `contract_version: v1.0.0` in scorecard metadata.
 
 ---
 

package/presets/cursor/agents/reviewer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — reviewer v0.5.0
+# Agent Contract — reviewer v1.0.0
 
 ## Role
 
@@ -204,7 +204,7 @@ Apply these detailed checks based on the detected stack:
 
 ---
 
-## Scorecard integration (v0.5.0)
+## Scorecard integration (v1.0.0)
 
 When the orchestrator requests evaluation, produce scores for all 8 criteria in
 `docs/agent-scorecard.md`:
@@ -213,7 +213,7 @@ When the orchestrator requests evaluation, produce scores for all 8 criteria in
 2. Minimal diff (20%)
 3. Tests present and passing (15%)
 4. No regressions (15%)
-5. Code conventions (10%)
+5. Code conventions (5%)
 6. Documentation updated (5%)
 7. Context discipline (5%)
 8. Complexity diffusion / cc-gain (5%)
@@ -222,7 +222,7 @@ When the orchestrator requests evaluation, produce scores for all 8 criteria in
 
 Map review verdict to scorecard verdict: `approved` → PASS, `approved with warnings` → REVISE (if warnings are material), `blocked` → REJECT.
 
-Invoke skill `evaluation` and run `scorecard record` with agent `reviewer`, model used, and `contract_version: v0.5.0`.
+Invoke skill `evaluation` and run `scorecard record` with agent `reviewer`, model used, and `contract_version: v1.0.0`.
 
 ---
 

package/presets/cursor/agents/security-reviewer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — security-reviewer v0.5.0
+# Agent Contract — security-reviewer v1.0.0
 
 ## Role
 

package/presets/cursor/agents/task-coach.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — task-coach v0.5.0
+# Agent Contract — task-coach v1.0.0
 
 ## Role
 

package/presets/cursor/agents/tester.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — tester v0.5.0
+# Agent Contract — tester v1.0.0
 
 ## Role
 

package/presets/cursor/commands/cc/api-contract.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the API contract workflow for public interface changes,
+  Run the API contract workflow for public interface changes,
   compatibility constraints, contract tests, documentation, and review.
 ---
 
@@ -20,6 +20,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 role)
 
 Invoke the `task-coach` subagent via the Task tool.
@@ -68,3 +82,7 @@ Invoke the `reviewer` subagent via the Task tool.
 
 Block on missing contract tests, undocumented breaking changes, or docs/OpenAPI
 drift.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

package/presets/cursor/commands/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.
 ---
 

package/presets/cursor/commands/cc/backlog.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Author BACKLOG.md — wayfinding, grilling, create or append items,
+  Author BACKLOG.md — wayfinding, grilling, create or append items,
   validate with openspec, and plan OpenSpec change folders for /cc-openspec.
 ---
 

package/presets/cursor/commands/cc/clarify.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Re-explain the last deliverable in Task Card vocabulary when it did not land.
+  Re-explain the last deliverable in Task Card vocabulary when it did not land.
 ---
 
 # Clarify Workflow

package/presets/cursor/commands/cc/council.md

@@ -85,3 +85,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/cursor/commands/cc/db-migration.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the database migration workflow for schema/data changes,
+  Run the database migration workflow for schema/data changes,
   operational sequencing, tests, and review.
 ---
 
@@ -21,6 +21,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 role)
 
 Invoke the `task-coach` subagent via the Task tool.
@@ -69,3 +83,7 @@ Invoke the `reviewer` subagent via the Task tool.
 
 Block on missing migration tests, missing data-risk notes, undocumented
 deployment sequencing, or model/migration drift.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

package/presets/cursor/commands/cc/explore.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Map the repository and recommend the next CodeConductor slash command. Read-only.
+  Map the repository and recommend the next CodeConductor slash command. Read-only.
 ---
 
 # Explore Workflow

package/presets/cursor/commands/cc/feature.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the full feature workflow — task validation, technical design,
+  Run the full feature workflow — task validation, technical design,
   implementation, testing, review, and documentation.
 ---
 
@@ -23,6 +23,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:
 
 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/cursor/commands/cc/fix.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the bug fix workflow — risk-based routing through task
+  Run the bug fix workflow — risk-based routing through task
   validation, implementation, testing, and optional review.
 ---
 
@@ -31,6 +31,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
@@ -146,3 +160,10 @@ Report: Task Card, Implementation Summary, regression test added, Review Report
 
 The fix is complete only when: the regression test passes, the full suite
 passes, and no CRITICAL review findings remain.
+
+Skills: `testing-tdd`, `evaluation`. Record `scorecard create --from-diff`.
+A small fix still needs a Task Card and a failing regression test first.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

package/presets/cursor/commands/cc/handoff.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Compact the session into gitignored `.codeconductor/sessions/handoff.md` (redact secrets).
+  Compact the session into gitignored `.codeconductor/sessions/handoff.md` (redact secrets).
 ---
 
 # Handoff Workflow

package/presets/cursor/commands/cc/iterative.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the advanced iterative workflow — Wayfinding AST discovery,
+  Run the advanced iterative workflow — Wayfinding AST discovery,
   Relentless Grilling, contract and spec design, TDD, council review, and docs.
 ---
 
@@ -23,6 +23,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/cursor/commands/cc/openspec.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run OpenSpec backlog delivery — validate BACKLOG.md, plan TaskCards,
+  Run OpenSpec backlog delivery — validate BACKLOG.md, plan TaskCards,
   orchestrate agents by phase, review gate, and update backlog state.
 ---
 
@@ -27,6 +27,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 — Validate (mandatory gate)
 
 Run:

package/presets/cursor/commands/cc/prototype.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Disposable spike in an isolated worktree. Not a merge candidate.
+  Disposable spike in an isolated worktree. Not a merge candidate.
 ---
 
 # Prototype Workflow

package/presets/cursor/commands/cc/refactor.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the refactor workflow — mandatory architectural justification,
+  Run the refactor workflow — mandatory architectural justification,
   test verification, risk-based implementation, and scope enforcement.
 ---
 
@@ -158,3 +158,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/cursor/commands/cc/review.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run a structured code review — produces a Review Report with
+  Run a structured code review — produces a Review Report with
   CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.
 ---
 
@@ -147,3 +147,7 @@ npx cc-codeconductor scorecard regression
 ```
 
 Map merge recommendation to scorecard verdict. Record outcome for trend tracking.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc:fix` or `/cc:feature`.

package/presets/cursor/commands/cc/scorecard.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Evaluate deliverable quality — scorecard, outcome tracking, regression
+  Evaluate deliverable quality — scorecard, outcome tracking, regression
   checklist, and aggregate stats.
 ---
 
@@ -26,6 +26,8 @@ Command: `scorecard` (fixed for this workflow — do not infer from user text)
 
 Use `$ARGUMENTS` as task id (e.g. `BC-001`) or read active item from `npx cc-codeconductor openspec status`.
 
+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`.
+
 ---
 
 ## Step 2 — Create scorecard with auto-signals

package/presets/cursor/commands/cc/security.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the authorized defensive security workflow — domain
+  Run the authorized defensive security workflow — domain
   security-* skills, authorization gate, risk-based routing, hardening, and review.
 ---
 
@@ -177,3 +177,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.