writing-plans

To convert a software spec into an implementation plan, use this skill to break down features into bite-sized tasks. It generates a comprehensive plan specifying file touchpoints, tests, design references, and commit milestones for thorough coding preparation.

The best way to document task breakdowns for a refactor is generating a standardized plan file. This skill enforces a naming convention and structures the document with explicit file changes, verification steps, and commit milestones to ensure alignment with the intended design.

Yes, you need a fully written spec before implementation planning, because this skill translates existing written specifications into actionable coding tasks. It does not generate the initial spec itself, but rather structures your existing design references into tasks.

Yes, you can use this implementation planning approach for complex bug fixes, as well as software features and refactors. It applies to any project requiring thorough planning before coding, mapping out the necessary file touchpoints and verification steps.

To structure implementation plans with file changes and tests, this skill enforces a standardized plan header and a specific file naming convention. It organizes the document into explicit task-by-task steps, specifying file touchpoints, required tests, and design references.

A limitation of using standardized plan files is the strict enforcement of the docs/plans/YYYY-MM-DD-<feature-name>.md naming convention and header structure. Projects deviating from this specific documentation format or lacking an initial written spec cannot utilize this planning approach.