sprint-plan

## Phase 0: Parse Arguments Extract the mode argument (`new`, `update`, or `status`) and resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `.claude/docs/director-gates.md` for the full check pattern. --- ## Phase 1: Gather Context 1. **Read the current milestone** from `production/milestones/`. 2. **Read the previous sprint** (if any) from `production/sprints/` to understand velocity and carryover. 3. **Scan design documents** in `design/gdd/` for features tagged as ready for implementation. 4. **Check the risk register** at `production/risk-register/`. --- ## Phase 2: Generate Output For `new`: **Generate a sprint plan** following this format and present it to the user. Do NOT ask to write yet — the producer feasibility gate (Phase 4) runs first and may require revisions before the file is written. ```markdown # Sprint [N] -- [Start Date] to [End Date] ## Sprint Goal [One sentence describing what this sprint achieves toward the milestone] ## Capacity - Total days: [X] - Buffer (20%): [Y days reserved for unplanned work] - Available: [Z days] ## Tasks ### Must Have (Critical Path) | ID | Task | Agent/Owner | Est. Days | Dependencies | Acceptance Criteria | |----|------|-------------|-----------|-------------|-------------------| ### Should Have | ID | Task | Agent/Owner | Est. Days | Depend...