writing-plans

Implementation plans are generated from specs by decomposing multi-step software tasks into bite-sized, test-driven steps. This process maps exact files, tests, and validation commands before any code changes begin, ensuring clear sequencing and execution order.

Task decomposition for multi-file refactors breaks large requests into small, testable tasks with clear sequencing. Each task maps to exact files, tests, docs, and validation steps, helping engineers move from requirements to execution with confidence.

Requirements analysis for bug fixes and cross-file feature work is supported by generating detailed implementation plans. It applies to multi-step software tasks that require careful coordination, reducing guesswork and rework.

Test driven development steps are mapped by generating placeholder-free instructions with exact commands and explicit file mapping. This ensures an engineer can follow the execution-ready plan without prior context.

An implementation plan is needed for software design tasks involving multi-step execution, refactors, or cross-file feature work. Generating a plan before coding begins reduces guesswork by providing clear decomposition and execution order.

Engineers new to a codebase benefit from implementation plans that provide clear decomposition and execution order. Placeholder-free instructions with exact file mapping and validation steps allow them to execute multi-step software tasks confidently.