write-plan

Converting design specs into actionable implementation checklists requires decomposing complex software tasks into ordered, dependency-aware execution steps. The process ensures every step has explicit success criteria, file-level impact analysis, and concrete verification commands.

Verification-first planning is an approach that ensures every step of an implementation plan has a concrete, testable outcome rather than vague progress markers. It prevents ambiguous execution by requiring explicit definition of success criteria and verification commands for each phase.

Sequencing multi-file refactoring steps to keep the build green involves breaking complex features into ordered, checkpointed steps with clear dependencies. This structured sequencing requires file-level impact analysis and concrete verification commands at each phase before proceeding.

You can generate a step-by-step implementation plan from a PRD by using structured sequencing to break down the approved design into granular, verifiable execution steps. The plan will include dependency-aware checkpoints and specific verification commands for each task.

This planning approach requires an approved design specification or PRD to function effectively. It is designed to convert existing, high-level design specifications into verifiable implementation plans, rather than to generate requirements or design documents from scratch.

Implementation plans often have vague progress markers when they lack verification-first design, which ensures every step has a concrete, testable outcome. Incorporating explicit success criteria, file-level impact analysis, and concrete verification commands resolves this ambiguity.