writing-plans

To create an implementation plan from a spec, decompose requirements into concrete tasks with clear boundaries. Document specific files to touch, tests to write, documentation updates, and commit steps, then save the plan to a standardized markdown file path.

Planning a multi-subsystem software project requires decomposing complex specifications into separate, executable plan documents. This structured approach prevents ambiguity by defining clear boundaries, specific files to modify, and test requirements for each subsystem before coding begins.

Break down project requirements into executable tasks by applying Test-Driven Development principles. Structure each plan step to include writing tests first, touching specific files, updating documentation, and making frequent commits to keep the project history clean.

Structured task planning is designed for cross-functional collaboration. It produces comprehensive, step-by-step plans from specs that can be reviewed and executed by engineers, testers, and documentation teams to ensure alignment across all project members.

You should not use a single implementation plan when a spec covers multiple subsystems. Instead, decompose the complex project into separate, executable plan documents to maintain clear boundaries and prevent scope creep during development.

An implementation plan should follow DRY and YAGNI standards to keep git history clean. Structure the plan to enforce frequent, logical commits, detailing which files to touch and tests to write at each step of the task decomposition process.