What problem does it solve? Turning a technical design into an actionable implementation sequence is error-prone: stages get missed, dependencies stay implicit, and approval boundaries blur. This Skill converts a design.md document into a compact, ordered plan.md that downstream executors and QA reviewers can consume without reinterpretation. ## Core Features & Use Cases - Staged Plan Generation: Produces plan.md with an ordered stage table, explicit dependencies, per-stage validation notes, and approval boundaries before code-touching work. - Open Question Surfacing: Carries unresolved design questions marked "Needed Before: execution" into the plan's Approval Notes so users see them before approving affected stages. - Planner and Macro-Plan Modes: Acts as the terminal stage for planner objectives (stopping at lifecycle_status planned) and supports approved macro-plan-first routes that decompose work into non-executable chunks. - Fix Stage Requests: Appends bounded fix stages scoped to confirmed review findings without rebuilding the whole plan. - Use Case: After finishing a design for a new API endpoint, run this stage to get a three-stage execution plan with validation checkpoints, then stop for approval before any code is written. ## Quick Start Ask the sddl orchestrator to run the planning stage on the current change's design.md to produce an executable staged plan for review.