Use Cases
After receiving a new feature specification from a product manager, the development team uses this skill to transform it into an executable step-by-step implementation plan. The skill first checks if the scope is too large (splitting into sub-projects if needed), then plans the file structure, decomposes tasks into 2-5 minute micro-steps (write test→run fail→implement→run pass→commit), providing precise code examples and verification commands for each step. The resulting plan document can be executed task-by-task by sub-agents or within the same session, significantly reducing decision-making costs during implementation.
When engineers face complex bugs requiring fixes across multiple files, this skill systematizes the debugging and fixing process into a plan. The skill analyzes affected subsystems, maps files needing modification along with their responsibility boundaries, and designs repair steps incorporating TDD cycles. Each step includes precise interface definitions and test verification methods, ensuring fixes don't introduce regressions. The plan includes a self-review mechanism to check specification coverage and type consistency, ultimately delivering an ordered task list that can be executed independently.
Skill File
Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
docs/superpowers/plans/ directory.Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.