cc-codeconductor 1.1.0 → 1.3.0

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

@@ -1,58 +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`.
 
-`BLOCKED` can return to `READY` when resolved. Reviewer rejection: `REVIEW` → `IN_PROGRESS`.
+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.
 
-## CLI commands
+Status machine: `TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW` → `DONE`
+→ Archive. `BLOCKED` returns to `READY`. Reviewer rejection: `REVIEW` →
+`IN_PROGRESS`.
 
-```bash
-npx cc-codeconductor openspec validate   # gate — must pass before delivery
-npx cc-codeconductor openspec scan
-npx cc-codeconductor openspec plan BC-001
-npx cc-codeconductor openspec status
-npx cc-codeconductor openspec next
-```
+## Common Rationalizations
 
-## OpenSpec folders
+| 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. |
 
-Each item generates `openspec/changes/<slug>/` with `proposal.md`, `design.md`, `tasks.md`, `specs/` — compatible with Fission-AI OpenSpec layout (no external CLI required).
+## Red Flags
 
-## Agent phases
+- Implementing while analyze reports CRITICAL
+- Archive without a PASS scorecard when review is required
+- Acceptance like "improve UX" with no measurable check
 
-| Phase | Agent |
-|-------|-------|
-| discover | repo-explorer |
-| design | architect |
-| test | tester |
-| implement | implementer |
-| review | reviewer |
+## Verification
 
-When Global `TDD required: yes`, test runs before implement.
-
-## Reject vague backlog
-
-Do not process items with acceptance like "improve UX" or "fix bugs". Require verifiable criteria.
+- [ ] `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/claude/skills/pagespeed-perf/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: pagespeed-perf
-version: 1.0.0
 name: PageSpeed Performance Audit
 description: >
   Web Performance Engineering — analyzes Core Web Vitals using the PageSpeed
@@ -32,7 +31,7 @@ inputs:
   - name: url
     type: string
     required: true
-    description: Full URL to audit (must include scheme: https://...)
+    description: "Full URL to audit (must include scheme: https://...)"
   - name: strategy
     type: string
     required: false

package/presets/claude/skills/python/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python
-version: 1.0.0
 name: Python
 description: >
   Python development best practices: clean code, patterns,

package/presets/claude/skills/python-django-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-django-stack
-version: 1.0.0
 name: Python Django Stack
 description: >
   Python and Django conventions for multi-tenant SaaS POS projects:

package/presets/claude/skills/python-fastapi-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-fastapi-stack
-version: 1.0.0
 name: Python FastAPI Stack
 description: >
   FastAPI conventions for REST APIs: routers, Pydantic v2 schemas, dependency

package/presets/claude/skills/security/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: security
-version: 1.0.0
 name: Security
 description: >
   Provides expert knowledge for implementing and reviewing application security following OWASP Top 10 (2021), with stack-specific patterns for Spring Boot, Django, Next.js, and Astro.

package/presets/claude/skills/spring-boot-feature/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-feature
-version: 1.0.0
 name: Spring Boot Feature Creation
 description: >
   Guides the creation of complete Spring Boot features following a structured,

package/presets/claude/skills/spring-boot-kotlin/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-kotlin
-version: 1.0.0
 name: Spring Boot + Kotlin
 description: >
   Provides expert knowledge of Spring Boot conventions, Kotlin idioms, and MVC

package/presets/claude/skills/sqlalchemy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: sqlalchemy
-version: 1.0.0
 name: SQLAlchemy
 description: >
   SQLAlchemy 2.x patterns for async FastAPI projects: models, sessions, queries,

package/presets/claude/skills/testing-strategy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: testing-strategy
-version: 1.0.0
 name: Testing Strategy
 description: >
   Provides expert knowledge of the testing pyramid, test design principles,

package/presets/claude/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/claude/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/codex/AGENTS.md

@@ -64,20 +64,24 @@ Skipping any step is not an optimization. It is a defect.
 
 ## Trigger Phrases
 
-Codex does not load custom slash commands from this preset. Use these natural
-language patterns to activate each workflow:
+Invoke workflows as Codex skills (`$cc-feature`, `$cc-openspec`, …). Custom
+prompts under `~/.codex/prompts` are deprecated. Natural-language phrases still
+work:
 
-| Workflow     | Trigger phrase                                     |
+| Workflow     | Skill / trigger                                    |
 | ------------ | -------------------------------------------------- |
-| Full feature | "Run the feature workflow for: [description]"      |
-| Bug fix      | "Run the fix workflow for: [description]"          |
-| Refactor     | "Run the refactor workflow for: [scope]"           |
-| API contract | "Run the API contract workflow for: [change]"      |
-| DB migration | "Run the database migration workflow for: [scope]" |
-| Code review  | "Run a structured review of: [target]"             |
-| Test plan    | "Create a test plan for: [scope]"                  |
-| Task intake  | "Help me define a Task Card for: [vague request]"  |
-| PageSpeed    | "Run a PageSpeed audit for: [url]"                 |
+| Full feature | `$cc-feature` or "Run the feature workflow for:"   |
+| Bug fix      | `$cc-fix`                                          |
+| Refactor     | `$cc-refactor`                                     |
+| API contract | `$cc-api-contract`                                 |
+| DB migration | `$cc-db-migration`                                 |
+| Code review  | `$cc-review`                                       |
+| Test plan    | `$cc-test-plan`                                    |
+| TDD cycle    | `$cc-tdd-cycle`                                    |
+| Backlog      | `$cc-backlog`                                      |
+| OpenSpec     | `$cc-openspec`                                     |
+| Scorecard    | `$cc-scorecard`                                    |
+| PageSpeed    | `$cc-pagespeed` or "PageSpeed audit"               |
 
 ---
 
@@ -1036,11 +1040,12 @@ Contract version:** v0.1.0 **Date:** [YYYY-MM-DD] **Evaluator:** [human name or
 | --- | --------------------------------- | ------ | ----------- | ----- |
 | 1   | Acceptance criteria met           | 30%    |             |       |
 | 2   | Minimal diff (no scope creep)     | 20%    |             |       |
-| 3   | Tests present and passing         | 20%    |             |       |
+| 3   | Tests present and passing         | 15%    |             |       |
 | 4   | No regressions introduced         | 15%    |             |       |
-| 5   | Code follows project conventions  | 10%    |             |       |
+| 5   | Code follows project conventions  | 5%     |             |       |
 | 6   | Documentation updated if required | 5%     |             |       |
 | 7   | Context discipline                | 5%     |             |       |
+| 8   | Complexity diffusion (cc-gain)    | 5%     |             |       |
 
 **Weighted score:** [calculated] **Pass threshold:** 2.0
 

package/presets/codex/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.
 ---
 
@@ -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/codex/skills/android/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: android
-version: 1.0.0
 name: Android + Kotlin (Jetpack Compose & Media3)
 description: >
   Provides expert knowledge for building modern native Android apps using Kotlin, Jetpack Compose, Material Design 3, MVI architecture, Hilt dependency injection, and Media3/ExoPlayer.

package/presets/codex/skills/api-versioning/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: api-versioning
-version: 1.0.0
 name: API Versioning
 description: >
   Provides expert knowledge for designing, implementing, and managing REST API

package/presets/codex/skills/backlog/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: backlog
+description: >
+  Guides agents through authoring BACKLOG.md and OpenSpec change folders.
+  Use when running /cc-backlog or /cc:backlog, creating or appending backlog
+  items, or preparing work for /cc-openspec. Delivery is skill openspec.
+---
+
+# Backlog authoring
+
+## Overview
+
+Create or append `BACKLOG.md`, then `openspec validate` / `plan`. Do not deliver
+the item here.
+
+## When to Use
+
+- `/cc-backlog`, first backlog in a repo, or appending `### BC-xxx` items
+
+**NOT** for executing an item (`openspec`) or for scorecards (`evaluation`).
+
+## Process
+
+1. If `graphify-out/graph.json` exists, `graphify query "<objectives>"`. Then
+   `repo-explorer`. Scope names real files.
+2. Invoke `task-coach`. One grilling question per assumption. Reject vague
+   acceptance ("improve UX"). At most 3 `[NEEDS CLARIFICATION]`.
+3. `ccep evaluate --command backlog`. If `stop`, wait for the human.
+4. Create `BACKLOG.md` from `presets/templates/BACKLOG.md` or append under
+   `## Items`. Do not rewrite `## Global` or `## Archive`.
+5. Next ID = max numeric suffix in Items + Archive + 1, zero-padded (`BC-013`).
+6. `bun run dev openspec validate` (or `npx cc-codeconductor`). Fix until valid.
+7. `openspec plan BC-xxx` for each **new** item this run. Then tell the user
+   to run `/cc-openspec`.
+
+Required sections: `## Global`, `## Items`, `## Archive`. Each item:
+`### BC-001 | Title` with Priority, Status (`READY` after grilling), Type,
+Depends on, Description, Scope, Out of scope, Acceptance.
+
+Local artifacts (`BACKLOG.md`, `openspec/`, `.codeconductor/openspec-state.json`)
+are gitignored in consumer projects. Do not `git add` them.
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+| --- | --- |
+| This fix is small; skip the Task Card | Every item needs measurable acceptance. |
+| I'll validate later | Do not plan until `openspec validate` passes. |
+| Archive can be rewritten | Archive is history. Never rewrite or re-execute. |
+
+## Red Flags
+
+- Acceptance that cannot fail a check
+- Editing `openspec-state.json` by hand
+- Planning an invalid backlog
+
+## Verification
+
+- [ ] `openspec validate` exit 0
+- [ ] New items have `FR`/`SC`-ready measurable acceptance
+- [ ] User pointed at `/cc-openspec` for delivery

package/presets/codex/skills/cc-api-contract/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: cc-api-contract
+description: Run the API contract workflow for public interface changes, compatibility constraints, contract tests, documentation, and review.
+---
+
+# api-contract
+
+Invoke as `$cc-api-contract`. The user request follows the skill mention.
+
+# API Contract Workflow
+
+API contract request: $ARGUMENTS
+
+## Step 0 — CCEP Bootstrap
+
+Command: `api-contract` (fixed for this workflow — do not infer from user text)
+
+1. Run: `npx cc-codeconductor ccep parse --command api-contract "$ARGUMENTS" --output json`
+2. Run: `npx cc-codeconductor ccep resolve --command api-contract "$ARGUMENTS" --output json`
+3. Run: `npx cc-codeconductor ccep profile api-contract --output json`
+4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command api-contract --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+
+---
+
+## 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)
+
+Adopt the `task-coach` role as defined in `AGENTS.md`.
+
+The Task Card must classify the task as high risk by default and include the
+affected public interface, request/response examples, compatibility notes,
+versioning impact, consumer impact, contract tests, and docs acceptance
+criteria.
+
+**STOP here. Show the completed Task Card and wait for human confirmation.**
+
+---
+
+## Step 2 — Technical Plan (Architect role)
+
+Adopt the `architect` role as defined in `AGENTS.md`.
+
+Define the API contract, validation strategy, compatibility behavior, docs or
+OpenAPI changes, and reviewer blocking conditions.
+
+**STOP here. Show the Technical Plan and wait for explicit human approval.**
+
+---
+
+## Step 3 — Implementation (Implementer role)
+
+Adopt the `implementer` role as defined in `AGENTS.md`.
+
+Apply the minimal diff, preserve compatible behavior unless explicitly approved
+as breaking, and update only the planned files.
+
+---
+
+## Step 4 — Contract Tests (Tester role)
+
+Adopt the `tester` role as defined in `AGENTS.md`.
+
+Add or update tests for request shape, response shape, status/error behavior,
+and backward compatibility.
+
+---
+
+## Step 5 — Review (Reviewer role)
+
+Adopt the `reviewer` role as defined in `AGENTS.md`.
+
+Block on missing contract tests, undocumented breaking changes, or docs/OpenAPI
+drift.
+
+## Next
+
+Run `$cc-review` on the diff before merging.

package/presets/codex/skills/cc-backlog/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: cc-backlog
+description: Author BACKLOG.md — wayfinding, grilling, create or append items, validate with openspec, and plan OpenSpec change folders for /cc-openspec.
+---
+
+# backlog
+
+Invoke as `$cc-backlog`. The user request follows the skill mention.
+
+# Backlog Authoring Workflow
+
+Objectives: $ARGUMENTS
+
+Create or append valid `BACKLOG.md` items and OpenSpec change docs. Do **not**
+deliver implementation — that is `/cc-openspec`.
+
+---
+
+## Step 0 — CCEP Bootstrap
+
+Command: `backlog` (fixed for this workflow — do not infer from user text)
+
+1. Run: `npx cc-codeconductor ccep parse --command backlog "$ARGUMENTS" --output json`
+2. Run: `npx cc-codeconductor ccep resolve --command backlog "$ARGUMENTS" --output json`
+3. Run: `npx cc-codeconductor ccep profile backlog --output json`
+4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command backlog --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+
+---
+
+## Step 1 — Wayfinding (repo-explorer)
+
+If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"` (and
+`graphify path` / `graphify explain` when needed). Then invoke `repo-explorer`
+to map modules, conventions, and impact radius. Do not write `BACKLOG.md` in
+this step. Record a Repo Map so Scope names real files or modules.
+
+---
+
+## Step 2 — Relentless Grilling (task-coach)
+
+Invoke `task-coach`. Produce complete backlog item fields: title, type, risk,
+scope, description, out of scope, measurable acceptance criteria.
+
+Every assumption must survive one grilling question. Reject vague acceptance
+("improve UX", "fix bugs").
+
+If any field is missing or ambiguous, ask one clarifying question at a time.
+
+**STOP here.** Unresolved grilling questions populate `questionsForUser` in the
+CCEP-1 `planner-output`; `ccep evaluate --command backlog` halts until a human
+answers. Do not write `BACKLOG.md` until that confirmation.
+
+---
+
+## Step 3 — Write or append BACKLOG.md (docs)
+
+Apply skill `backlog`.
+
+- If `BACKLOG.md` is absent, create it from the canonical template
+  (`presets/templates/BACKLOG.md`). Set Global `Product` from `package.json`
+  `name` when present.
+- If it exists, append new `### BC-xxx` items under `## Items`. Do not rewrite
+  `## Global` or `## Archive`.
+- Next ID = max `BC-NNN` across Items and Archive, plus one.
+- New items: Status `READY`, Progress `0%`, measurable Acceptance checklist.
+
+Do **not** `git add` `BACKLOG.md` or `openspec/`.
+
+---
+
+## Step 4 — Validate (mandatory gate)
+
+Run:
+
+```bash
+npx cc-codeconductor openspec validate
+```
+
+If validation fails:
+
+1. List all errors and recommendations from the CLI output.
+2. Show the canonical BACKLOG.md structure (## Global, ## Items, ### BC-001 | Title, Priority, Status, Type, Depends on, Description, Scope, Acceptance).
+3. Fix the file and re-run validate. **STOP** planning until valid.
+
+---
+
+## Step 5 — Plan new items
+
+For each **new** `BC-xxx` from this run:
+
+```bash
+npx cc-codeconductor openspec plan <BC-id>
+```
+
+Show TaskCards and `openspec/changes/<slug>/` (proposal, design, tasks, specs).
+
+---
+
+## Completion
+
+Report: item IDs added, validate result, change folder paths.
+
+Tell the user to run `/cc-openspec` (optionally `/cc-openspec BC-xxx`) to
+deliver. Do not start delivery in this workflow.
+
+Apply skill `backlog` for create/append rules. Apply skill `openspec` only for
+format and state-machine reference.