writing-plans

# writing-plans Turn an approved spec into an executable plan. Routed to by `/feature` (after spec approval) and `/sprint`. ## Pre-flight Read these, or STOP and surface the gap — never plan against an unapproved or missing spec: - `<project-root>/.codearbiter/specs/<slug>.md` — the approved brainstorming spec. The single source of acceptance criteria. Absent or unapproved → STOP and route back to `/feature`. - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `<project-root>/.codearbiter/tech-stack.md` — file layout, build/test/lint invocations. A verification step cites a real command from here, never a guess. - `<project-root>/.codearbiter/coding-standards.md` — structure and naming, so a task names the right path. **If `--farm` was requested:** check that `FARM_API_KEY` is set in the environment (or `.env` at `tools/.env`). If absent, BLOCK immediately — cite [includes/farm.md](../../includes/farm.md) for setup instructions. Do not proceed; the farm dispatcher cannot run without an API key. Model selection happens later (at dispatch time in `subagent-driven-development`), so no model research is needed here. ## Phase 1 — Criterion extraction · gate: BLOCK Lift every acceptance criterion from the spec verbatim and assign each a stable ID (`AC-01`, `AC-02`, …). This list is the coverage ledger for the whole plan — Phase 4 checks the task set against it. A criterion the spec leaves ambiguous is a `[CONFIRM...