writing-plans

To break down a multi-step software implementation task, generate a comprehensive plan using a fixed template that enforces bite-sized, 2-5 minute tasks. This creates a clear roadmap detailing files to modify, tests to write, and documentation steps before coding begins.

The best way to plan TDD and version-control steps is using a standardized implementation plan template. This ensures each task explicitly lists tests to write, code changes, documentation updates, and commit guidelines in a structured, task-by-task format.

You create an implementation plan document by applying a fixed plan template that covers execution from testing to deployment. The resulting plan is automatically saved as a markdown file at docs/plans/YYYY-MM-DD-<feature-name>.md for team reference.

Yes, a structured task-breakdown plan supports guided workflows for subagent-driven or parallel execution. The generated plan provides the explicit, step-by-step guidance necessary to hand off and review tasks across multiple execution agents.

Generating an implementation plan requires no predefined dependencies or environment setup, as it operates independently to produce a markdown roadmap. It focuses on structuring task breakdown, TDD steps, and commit guidelines rather than executing code.

You should avoid using a fixed template for implementation planning when your software work does not require explicit step-by-step guidance or structured task breakdowns. It is specifically designed for multi-step tasks needing detailed roadmaps from testing to deployment.