writing-plans

To create an implementation plan from a spec, generate a complete task breakdown specifying exact file paths, tests, documentation, and commit messages for multi-step projects. This translates vague requirements into concrete, task-by-task guidance.

The best way to break down multi-step software engineering tasks is to generate an end-to-end plan that enforces DRY and YAGNI principles. This approach lists exact files to touch, tests to write, and commit messages for incremental development.

Plan generation supports TDD workflows by integrating test-writing directly into the task breakdown. It provides specific test guidance alongside implementation steps, promoting best practices and ensuring incremental development for each project phase.

Yes, you can save generated feature plans to docs/plans with the current date in a YYYY-MM-DD-<feature-name>.md format. This ensures plan persistence and traceability across your software engineering project lifecycle.

No external dependencies are required to generate executable task plans. The skill operates independently to translate requirements into task lists, providing a repeatable plan template without needing additional packages or external modules.