plan

To break down a complex software feature into verifiable steps, generate a structured implementation plan that decomposes tasks into 2-5 minute actions with specific file paths and verification commands.

Test-driven development planning for software implementation is a structured approach that mandates a TDD cycle for every coding task, ensuring your roadmap produces clear, logical, and verifiable code.

You generate a structured implementation plan for a new API endpoint by creating a markdown document that includes goals, architecture, and step-by-step tasks with precise file path documentation for all proposed changes.

Yes, you can plan tasks in your local workspace without external dependencies, as the approach requires no dependencies and operates entirely within your local development environment.

The best way to ensure precise documentation for code changes is to mandate specific file-path documentation for all proposed modifications directly within your structured markdown implementation plan.

You should not use a TDD-focused implementation plan when your coding tasks require exploratory prototyping without strict verification cycles, as this approach mandates test-driven development principles for every step.