plan-review-checklistlisted

# Plan Review Checklist ## 1. Use Case Coverage - [ ] **Total Coverage:** Every Use Case mapped to >= 1 Task? - [ ] **Traceability:** Coverage table exists? ## 2. Structure & Formalism - [ ] **Stub-First:** Every component has specific "Stub" and "Impl" phases/tasks? - [ ] **Dependencies:** Task order respects dependencies? - [ ] **Phasing:** Clear stages (Structure -> Logic -> Test)? ## 3. Task Descriptions - [ ] **Existence:** File exists for every task in `plan.md`? - [ ] **Naming:** Matches `task-{ID}-{SubID}-{slug}.md`? - [ ] **Sections:** Contains Goal, Changes, Test Cases, Acceptance Criteria? - [ ] **Depth:** Specific file paths and method signatures? (Without coding). - [ ] **Strict Mode:** Usage of `tdd-strict` specified for critical components/bugs? ## 4. Register (`documentation-standards` §5.5) - [ ] **Scan attached:** `scan_register.py docs/PLAN.md docs/tasks/task-<ID>-*.md --sections --terms docs/ARCHITECTURE.md` was run over **every** task file this plan produced, not a sample; `DETECTORS` shows none dead. `<ID>` is the Task ID from `docs/TASK.md` section 0. Task files carrying an earlier ID are the archive (`skill-archive-task` moves rotated documents into the same directory) and are out of this review's scope. - [ ] **Warns resolved:** zero `warn`, or each survivor carries a written reason. - [ ] **Reading pass covered:** every section of every task file appears in the worklist and was read for rules 3, 4 and 6. ## 5. Refe