writing-plans

To generate an implementation plan from a feature spec, feed the spec into the skill to automatically decompose the feature into concrete, testable steps detailing files, tests, docs, and commits.

End-to-end task decomposition breaks a feature into concrete, testable steps across software projects, detailing what to touch in code, tests, docs, and commits to create a full implementation plan.

Yes, you can create implementation plans without prior codebase knowledge because this skill generates context-free plans, allowing multi-step task decomposition even when the project structure is unfamiliar.

The best way to document engineering plans is to output a ready-to-run plan document saved to docs/plans/YYYY-MM-DD-<feature-name>.md, satisfying frontmatter metadata requirements for planning workflows.

No, this planning workflow requires no dependencies or environment setup, allowing you to directly run the skill on a feature request to generate a complete implementation plan document.

An automated engineering implementation plan includes detailed task decomposition specifying exactly which files to touch, what tests to write, documentation updates, and commits needed for the feature.