Use Cases
When a developer receives a new feature request, whether simple or complex, they can use the brainstorming skill to avoid blind coding. It guides exploration of project context, clarifies requirements through one-question-at-a-time dialogue, proposes multiple technical approaches with trade-offs, and finally writes a design document. This prevents the anti-pattern of skipping design for supposedly simple tasks and avoids rework caused by unexamined assumptions.
When working on an existing codebase, developers need to understand current structure before proposing changes. The brainstorming skill explores existing files, docs, and recent commits first, then designs improvements following existing patterns. When it finds issues like oversized files or unclear boundaries, it includes targeted improvements in the design while avoiding unrelated refactoring. The final output is a design document covering data flow, error handling, and testing plans.
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/specs/ and commit to GitSkill 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.