writing-plans

To generate an implementation plan for a new software feature, define the task and the system creates detailed, bite-sized steps. It outlines specific files to modify, test code snippets, exact commands with expected outputs, and commit instructions to facilitate TDD.

The best way to break down complex coding tasks for TDD is to generate comprehensive, bite-sized implementation plans. This approach provides exact commands with expected outputs and frequent commit instructions, ensuring structured test-driven development without assuming prior codebase context.

Yes, you can create a step-by-step coding plan without prior knowledge of the codebase. The generation process assumes minimal context of the problem domain, outlining specific files to modify and implementation snippets for engineers to execute.

Implementation planning does include specific test commands and expected outputs. The generated plans outline exact commands to run for each step, provide code snippets for tests and implementation, and detail commit instructions to ensure frequent commits.

You should use detailed task breakdown for software development when tackling complex features requiring structured execution. It is ideal for generating comprehensive, multi-step plans where specific file modifications, test snippets, and TDD workflows are needed to ensure clear, actionable instructions.