write-plan

To turn software design specs into verifiable implementation plans, you define goals, scope items, and acceptance criteria, then decompose them into sequential tasks. Each task lists exact files to modify, implementation steps, and single-file verification commands.

To decompose multi-step software features into verifiable tasks, break scope items down into self-contained units containing Files, Steps, and Verify sections. This ensures engineers execute work with zero assumed context and exact verification steps for each task.

Including decision points in feature design docs involves presenting blocking choices to the user during plan generation and recording the selected options in the final plan file. This ensures phase-driven development accounts for critical architectural decisions before implementation begins.

Yes, you need acceptance criteria and design docs to generate an implementation plan. This tool applies to scenarios where goals, scope items, and design or crystal documents are already available to decompose work into structured, verifiable tasks.

Yes, you can validate an implementation plan before starting development. The plan generation process triggers automated validation, checking the structured task sequence, decision points, and verification steps to ensure the plan is executable.

When planning phase-driven development with loosely specified goals, the limitation is that loosely specified requirements must be converted into structured goals and scope items first. The tool requires clearly defined acceptance criteria to properly decompose work into verifiable tasks.