writing-plans

To turn a software spec into an actionable implementation plan, provide the feature brief to generate a document detailing concrete task breakdowns, execution order, touched files, tests, and commit steps.

Break down a multi-step software feature by decomposing the spec into concrete tasks, assigning owners, defining an execution order, and outlining required testing considerations and validation steps.

The best way to plan code changes and tests is generating a change footprint that identifies which files to modify, new tests to add, and validation steps to execute before actual coding begins.

This implementation planning approach works specifically for multi-step software tasks requiring upfront design, applying task breakdown and testing considerations to reduce guesswork and rework during development.

You can outline documentation needs and suggested commit history during task breakdown, ensuring the generated implementation plan includes structured commit steps alongside the execution order.