writing-plans

To create a detailed implementation plan, generate step-by-step tasks providing exact file paths, code snippets for tests and implementations, and precise commands for verification and commits.

The best way to break down tasks is to structure the implementation plan with specific file modifications, test writing steps, and commit messages, ensuring adherence to TDD, DRY, and YAGNI principles.

Test-driven development planning works by guiding developers through the entire implementation process, starting from writing failing tests to final commits, while assuming minimal prior knowledge of the codebase.

Yes, you can use this planning approach because it provides contextual guidance and assumes minimal prior knowledge of the codebase or problem domain for the implementer executing the tasks.

A limitation of automated task breakdown is that it requires clear initial requirements to be effective, as it focuses on generating precise file modifications and test snippets rather than discovering project scope.

Yes, writing-plans supports generating commit messages and verification commands by providing precise commands for commits and exact code snippets for tests and implementations during task execution.