writing-plans

To generate a detailed implementation plan, define the multi-step software development task and let the system outline specific files to modify, code to write, tests to create, and commands to execute. This ensures developers have actionable steps with minimal context needed.

The best way to break down a coding feature is to generate bite-sized, actionable steps that include contextual documentation like file paths, code snippets, and testing instructions. This approach guides the entire development process from writing tests to the final commit.

Task breakdown works with TDD, DRY, and YAGNI principles by strictly requiring adherence to them during plan generation. This ensures the implementation steps outline only necessary code, prevent duplication, and prioritize writing tests before the actual development begins.

Yes, you can use this approach to plan user authentication features without prior context. The generated implementation plan provides comprehensive guidance, detailing exact file modifications, code snippets, and commit messages for developers to follow.

No, you do not need to manually write commit messages because the generated implementation plan includes them as part of the contextual documentation. This ensures clarity and consistency throughout the entire software development process.