heist

Plan the job before pulling it off. 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)

1. Feature spec (what to build) — PRD, conversation context, or user's brief. Defines scope, user stories, acceptance criteria.
2. 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 Crew 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.
3. 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 The Job, The Crew descriptions, and acceptance criteria.
4. 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. 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.

Output format

Write to docs/plans/NNNN-<slug>.md (zero-padded, next available). Create dir if missing.