writing-plans

To generate an implementation plan, define the feature scope and the Skill produces a detailed, step-by-step task breakdown outlining specific files, code, testing, and documentation requirements. This minimizes ambiguity and ensures all necessary context is provided for execution.

The best way to break down multi-step development tasks is using a standardized format that generates bite-sized, actionable steps. This includes contextual guidance on files to modify, code snippets, and testing procedures, adhering to TDD, DRY, and YAGNI principles for maintainable workflows.

Test-driven development fits into implementation plans by structuring the task breakdown to guide developers from writing failing tests to committing code. The plan outlines every step, ensuring testing procedures and documentation references are explicitly defined before implementation begins.

Yes, you can use this to plan documentation and testing requirements alongside code implementation. The generated plans provide necessary information on files to modify, code snippets, testing procedures, and documentation references, ensuring all development aspects are covered in a consistent task structure.

You need a detailed task breakdown for software development when starting a new feature or facing complex multi-step tasks. It ensures developers have all necessary context and guidance, preventing ambiguity by outlining specific files, testing, and documentation requirements before coding starts.