writing-plans

To turn a feature specification into an actionable implementation plan, provide a high-level spec to generate structured, task-level steps with proposed file changes, tests, and documentation. It outputs a structured markdown file ready for execution.

The best way to break down multi-step software tasks is to decompose complex work into bite-sized tasks aligned with TDD, DRY, and YAGNI principles. This approach specifies exact files to touch, tests to write, and testing methods, assuming zero codebase context.

Yes, the generated implementation plan includes test-driven development steps. It ensures plans follow DRY, YAGNI, and TDD principles by specifying the exact tests to write and detailing how to test each bite-sized task for multi-step features.

Yes, you can save task planning documentation directly to your repository. The skill outputs plan artifacts as structured markdown files to the docs/plans/YYYY-MM-DD-<feature-name>.md path, suitable for version control and team collaboration.

You need a structured plan for multi-step tasks when converting vague requirements into executable work for engineers and QA. It translates new feature specs into bite-sized, documented tasks to reduce ambiguity and accelerate delivery.