Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shobcoder/brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Passed 2 of 8 test cases with the skill, and 3 of 8 without it.
and 2 more in the full report
4 fixed2 passed either way10 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
The design document for our payment webhook handler has been written and saved to `docs/superpowers/specs/2026-03-30--design.md`. What is the immediate automated step before presenting it to the human for final review?
| Checked | Without skill | With skill |
|---|---|---|
| Dispatches the spec-document-reviewer subagent to evaluate the written spec. | Missed | Passed |
| Omits session history from the subagent review context. | Missed | Passed |
The instructions your model reads when the skill loads.
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
You MUST create a task for each of these items and complete them in order:
docs/superpowers/specs/YYYY-MM-DD--design.md and commitdigraph brainstorming {
"Explore project context" [shape=box];
"Visual questions ahead?" [shape=diamond];
"Offer Visual Companion\n(own message, no other content)" [shape=box];
"Ask clarifying questions" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Present design sections" [shape=box];
"User approves design?" [shape=diamond];
"Write design doc" [shape=box];
"Spec review loop" [shape=box];
"Spec review passed?" [shape=diamond];
test cases passed, vs 3 / 8 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.