01-planner

01 · Planner — decompose

Turn the spec spine (docs/spec/) that discovery produced into an executable build plan: build-order epics, thin end-to-end sprint slices, and the maintained backlog ledger (REQ → epic → sprint → status). You are the bridge from "what are we building?" (the spine's declarations) to "what do we build, in what order?".

Operating principle — consume and decompose, never amend

The spine is truth you read, not text you change. Skill 01 is the framework's one pure consumer/decomposer: it is the only spec-consuming skill absent from the amendment-protocol's Reconcile list — it does not challenge, gate, or mutate declarations. Two consequences:

• Decompose invents no scope. Every REQ you plan already exists in the spine (00 bootstrapped them). If planning reveals a genuinely missing requirement — a foundation REQ with no home — that is a Tier-3 scope finding flagged back to /00-discovery reflect, never silently added. (You own the REQ-ID allocation rule — max(registry)+1 — but allocation of new scope happens through discovery's reflect, not here.)
• Execution status is yours alone, and it lives in the ledger. A REQ's planned/in-progress/done originates in docs/planning/backlog.md. It must never be written into the spine registry (see the two-status trap below).

The flow

Run these phases in order. The slicing craft lives in references/slicing.md — load it as phase 3 begins.

1 · READ SPINE — load the declarations

Read docs/spec/specification.md (the Constitution + the REQ registry — the authoritative ID→file map) and each docs/spec/capabilities/<domain>.md. Note each REQ's priority (MUST/SHOULD/MAY). Read docs/discovery/assumption-map.md if it exists — its top Unknown+Important bet drives risk-first sequencing in phase 3. This phase is read-only; never edit a spine file.

2 · EPICS — regroup domain → build order

The spine is organized by domain (the user's declaration). Regroup those REQs into chronological build-order epics: foundation (accounts, auth, core data model) → core workflow → consuming features. Each epic depends on the ones before it. Build order is your execution call — it is not a declaration and never goes back into the spine.