plan-draftinglisted

# Plan Drafting Codified 2026-08-27 from the convergence retrospective on the extraction and score-cache plans. Those plans needed dozens of review rounds. Root causes: duplicated facts, derived counts, files with edits but no owner, unverified claims, and design gaps that surfaced one per round. ## Template Draft every plan with these sections, in this order: 1. **Context.** Why the plan exists. What it must produce. 2. **State as of \<date\>.** Every volatile world fact: tree status, caches, machine state, registry contents. Mark the date. Refresh this section when execution starts. Reviewers audit this section for freshness only. 3. **Decision register.** Every decision the plan makes, one line each: flag names, resolution orders, pass conditions, exclusions, ownership calls. Each line points to the section that carries the rationale. 4. **Design sections.** The rationale and the mechanics. Each fact is stated here once. 5. **Ownership table.** One table: file, stream, edit. Build it by enumerating every file the plan names anywhere. 6. **Wave structure.** Foundation, parallel streams, verifier (the parallelizable-plans rule). Reference the ownership table. Do not restate it. 7. **Verification.** Numbered checks. Each check names its command, its working directory, and its expected output shape. 8. **Boundaries.** What the plan does not do. ## Skeleton contract The skeleton must stand alone. Cold workflow agents draft the detail sections from it, with no access to th