writing-plans

To create a detailed implementation plan, break down multi-step development tasks into bite-sized actions. Outline specific files to modify, code snippets to implement, testing procedures, and commit instructions to ensure developers have clear, actionable steps before writing code.

The best way to structure task breakdowns for test-driven development is to generate bite-sized steps that explicitly include instructions for writing tests first, followed by minimal code implementation, and ending with structured commit messages to maintain TDD and DRY principles.

Yes, this implementation planning approach works for developers with limited context by providing comprehensive contextual information. It details exactly which files to touch, necessary testing procedures, and documentation references needed to execute the task efficiently.

You can generate code snippets and commit instructions by creating an implementation plan that enforces YAGNI principles. The plan specifies the exact minimal code to implement, the tests to write, and the commit messages to use for each step of the feature.

You need a step-by-step implementation plan when starting a new feature that requires task breakdown. It ensures you outline every file to modify, exact tests to write, and commit instructions, providing necessary context and structure for a complex development process.

A limitation of generating implementation plans for complex tasks is that granularity depends on the provided context. While the plan enforces TDD, DRY, and YAGNI principles, developers must still manually execute the bite-sized steps, write the code snippets, and run the testing procedures.