writing-plans

To generate a TDD implementation plan, the Skill breaks down complex software features into bite-sized, actionable steps. These steps specify writing failing tests, implementing minimal code, running tests, and committing changes with exact file paths and commands.

Task breakdown granularity in a development workflow plan refers to dividing large implementation processes into small, actionable steps. This ensures engineers follow TDD, YAGNI, and DRY principles by focusing on minimal code increments and frequent commits.

To ensure your implementation plan includes exact file paths and commands, use a planning Skill that provides comprehensive documentation for each granular task. It specifies exact file paths, code snippets, commands, and expected outputs for every step.

Yes, you can use this planning approach for multi-step software development tasks. It is specifically designed to generate detailed, actionable implementation plans that guide engineers through the entire development workflow.

Yes, the generated plan enforces writing failing tests before code implementation. It defines granular tasks that explicitly require writing failing tests, implementing minimal code, running tests, and committing changes to adhere to TDD principles.