writing-plans

To break down a software feature spec into implementation tasks, this Skill decomposes high-level specifications into actionable steps covering design, code, tests, docs, and deployments across a single subsystem. It maps tasks to specific files and generates suggested commit messages.

Work breakdown structure for multi-step features involves decomposing a specification into discrete, bite-sized engineering tasks. This approach requires explicit task breakdown, file-structure mapping, testing steps, and saving version-controlled plan artifacts under docs/superpowers/plans.

You generate an implementation plan with file mapping and commit messages by providing a feature spec, which the Skill translates into a detailed plan. It defines which files will be created or modified and organizes task responsibilities alongside suggested commit messages.

No, this implementation planning approach is applicable for features that require decomposition across a single subsystem. It does not support planning work that spans multiple subsystems simultaneously.

Task decomposition plans are saved to a standardized location under docs/superpowers/plans with a date stamp formatted as YYYY-MM-DD-<feature-name>.md, ensuring consistent version-controlled plan artifacts for team alignment.

The best way to align product teams and engineers before coding begins is to translate high-level specs into detailed, actionable implementation plans. This ensures everyone is aligned by mapping tasks, files, tests, docs, and commits before development starts.