writing-plans

To break down multi-step software features, you create an executable implementation plan that specifies file changes, tests, documentation, and validation steps, structuring large tasks into a clear step-by-step roadmap.

The best way to plan file changes is by generating a detailed roadmap that lists required file modifications, testing methods, and documentation needs, ensuring all tasks are clear and testable before coding begins.

You create a task breakdown template that enforces TDD and DRY by structuring your roadmap with dedicated sections for tests, validation, and step-by-step implementation, storing the results as Markdown files.

Yes, this planning workflow supports storing implementation roadmaps as Markdown documentation by saving the generated plans directly under the docs/superpowers/plans directory for team alignment and review.

Yes, you can use this task planning method for cross-file changes, as it breaks down large tasks into small steps that list required file modifications and tests, supporting frequent commits and structured validation.

You need a structured implementation roadmap when planning multi-step software features, ensuring your team aligns on file changes, tests, and validation steps before starting the actual coding process.