What problem does it solve? Turning an approved spike or feature idea into a validated, chaptered implementation plan requires coordinating scaffolding, multi-reviewer validation, feedback triage, revision, and decision locking — a process that is error-prone and easy to shortcut when done ad hoc. ## Core Features & Use Cases - Plan scaffolding: Creates a new plan via the yolo new plan CLI with auto-assigned pNN- numbering inside the correct project subtree. - Per-chapter validate-loop: Authors each chapter, then runs validate-doc, triage-feedback, revise-doc, process-feedback, and lock-decisions until convergence (minimum 2 iterations, hard cap at 3). - Overall README pass: Validates the plan README end-to-end after all chapters converge, with captain approval gating any chapter reopening. - Use Case: After a spike on an auth refactor is approved, invoke this skill to scaffold the plan, author chapters in dependency order, run the baseline reviewer set (accuracy, architecture, integration, dx, scope), and produce a convergence summary with locked decisions and pending clusters. ## Quick Start Ask the agent to create an implementation plan named auth-refactor from the approved spike, and it will scaffold the plan, author and validate each chapter to convergence, and report a convergence summary.
