writing-plans

To generate an implementation plan, you provide a multi-step software development task, and the Skill breaks it down into bite-sized, 2-5 minute actionable steps. It outputs detailed documentation covering file modifications, code implementation, and commit strategies.

Breaking down a multi-file development task is handled by dividing the work into small, 2-5 minute steps. The generated plan specifies exact files to modify, code snippets to implement, testing procedures, and commit messages.

Yes, you can use TDD principles to plan code implementation automatically. The generated plans ensure adherence to Test-Driven Development (TDD), alongside DRY and YAGNI principles, guiding you through writing tests before implementing code.

The best way to create a coding plan with limited codebase context is using an automated task breakdown tool. It generates detailed implementation plans that reduce ambiguity and guide engineers through systematic code changes and testing.

Yes, the generated development plan includes commit messages and testing procedures. The comprehensive documentation specifies files to modify, code snippets, testing procedures, and commit strategies for each actionable step.

You should not use automated task breakdown for trivial single-file edits that require no testing or commit strategy planning. It is specifically designed for multi-step software development tasks requiring detailed documentation and strict adherence to TDD principles.