writing-plans

To break down a software feature spec, generate a comprehensive implementation plan detailing bite-sized task-level steps, explicit files to touch, tests to write, and a recommended commit sequence for developers.

Creating a TDD-aligned implementation plan involves producing bite-sized tasks that enforce DRY principles, detailing the exact tests to write alongside the code changes required for each specific development step.

Requirement analysis for feature development plans processes unclear or limited context by generating end-to-end steps covering code, tests, docs, and deployment, ensuring engineers know exactly what to touch and document.

Yes, this task planning approach enforces a disciplined workflow by requiring a dedicated worktree, applying DRY and TDD principles, and saving the generated plan to docs/plans/YYYY-MM-DD-feature-name.md for versioned reference.

Yes, you can use this implementation plan generator for multi-step tasks across code, tests, docs, and deployment, as it produces end-to-end plans covering all required file modifications and documentation handoffs.