blueprint

Turn a settled scope into an ordered build plan. Read the context, output a single Markdown file at docs/plans/NNNN-<slug>.md (zero-padded, next available index). Don't write code. Don't bundle multiple features.

Inputs to gather (in order, stop when enough)

Feature spec (what to build) — PRD, conversation context, or user's brief. Defines scope, user stories, acceptance criteria.
Architectural constraints (how it must be built) — scan docs/adr/ for accepted ADRs touching the area. ADRs are locked decisions: stack, paradigm, persistence model, integration style, auth, observability. Read every ADR whose subject overlaps the Files Affected set. List them in Sources. Plan must respect them — if the plan would violate an ADR, stop and surface the conflict to the user before writing.
Codebase shape — relevant files, framework, conventions. Use Glob/Grep/Read sparingly; depth proportional to feature size. If the PRD has a ## Glossary, use those terms verbatim in Summary, Files Affected descriptions, and acceptance criteria.
Operational constraints — deadlines, performance/security needs, feature-flag policy.

If feature spec is fuzzy → stop, tell user to run /grill-me or /to-prd first. Don't invent scope, and don't interview the user yourself: that is grill-me's job, so name it in the reply. If an architectural choice is unsettled (no ADR, no clear convention) → stop, tell user to run /compass first. Don't pick paradigms inside a plan.

Acceptance examples come from the PRD. If it has ## Acceptance Examples, copy them into the plan's Acceptance Criteria verbatim (ids, wording and (proposed) marks), the way Glossary terms travel. If a settled spec has none (an older PRD, or a brief that never went through to-prd), draft them in the same format from that spec and mark each rule (proposed). When a PRD exists, the approved ACs go back into it with the same ids (a to-prd "update the PRD"), so ids are only ever minted in one place.

Proposed ACs get a human read before code is held to them. Whenever any AC in the plan is still (proposed), copied or drafted, approving them is the plan's first Open Question. On approval, drop the marks in the plan and the PRD together so the two stay verbatim; that is the one change to the locked Acceptance Criteria section that needs no further OK.

Read testing-philosophy before choosing tiers and writing the Test Plan.