obra/superpowers@writing-plans

To generate an implementation plan, provide a feature name and requirements. The system outputs a comprehensive, task-by-task breakdown documenting exact files to touch, tests to write, and docs to update.

Task breakdown planning decomposes feature requirements into actionable, bite-sized tasks. It documents required files, tests, and documentation to ensure consistent, repeatable feature delivery across teams and repositories.

Implementation plans are saved to docs/plans using date-based filenames formatted as YYYY-MM-DD-<feature-name>.md, ensuring worktree-aware, consistent organization for team collaboration.

Yes, reusable feature-pattern templates support consistent feature delivery. These templates standardize the documentation of required files, tests, and commit history across multiple repositories.

Yes, the planning process supports optional components directories. It accommodates scripts, references, and assets as needed, alongside loading configuration from the SKILL.md frontmatter.

Planning documentation relies on date-based filenames and standard markdown templates. It requires a consistent docs/plans directory structure to maintain repeatable feature delivery across different repositories.