milestone-review

## Phase 0: Parse Arguments Extract the milestone name (`current` or a specific name) 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: Load Milestone Data Read the milestone definition from `production/milestones/`. If the argument is `current`, use the most recently modified milestone file. Read all sprint reports for sprints within this milestone from `production/sprints/`. --- ## Phase 2: Scan Codebase Health - Scan for `TODO`, `FIXME`, `HACK` markers that indicate incomplete work - Check the risk register at `production/risk-register/` --- ## Phase 3: Generate the Milestone Review ```markdown # Milestone Review: [Milestone Name] ## Overview - **Target Date**: [Date] - **Current Date**: [Today] - **Days Remaining**: [N] - **Sprints Completed**: [X/Y] ## Feature Completeness ### Fully Complete | Feature | Acceptance Criteria | Test Status | |---------|-------------------|-------------| ### Partially Complete | Feature | % Done | Remaining Work | Risk to Milestone | |---------|--------|---------------|------------------| ### Not Started | Feature | Priority | Can Cut? | Impact of Cutting | |---------|----------|----------|------------------| ## Quality Metrics - **Open S1 Bugs**: [N] -- [List] - **Open S2 Bugs**: [...