writing-plans

To generate an implementation plan, define the multi-step software development task and let the skill produce detailed, actionable instructions covering exact file modifications, code snippets, testing procedures, and commit strategies. It breaks down complex features into bite-sized tasks for efficient execution by engineers with minimal context.

The best way to break down complex features is to generate a comprehensive plan that provides precise instructions including exact file paths, code implementation, and testing instructions. This approach ensures tasks are small and manageable, reducing ambiguity for engineers who need minimal prior context.

TDD fits into detailed implementation planning by guiding the task sequence from writing failing tests to committing code. The generated plan ensures adherence to TDD principles through bite-sized task granularity, providing engineers with precise testing procedures and commit strategies for each step.

Yes, you can use this approach to plan exact file modifications and commit strategies. The generated implementation plans include exact file paths, code snippets, testing instructions, and commit messages, ensuring engineers can follow each step precisely without needing additional context.

You need a detailed implementation plan when starting a new feature that requires multi-step software development and strict adherence to YAGNI and DRY principles. It provides bite-sized tasks with exact file paths and testing instructions to minimize ambiguity and reduce the need for prior context.