Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →guanyang/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 13 of 21 test cases with the skill, and 4 of 21 without it.
and 16 more in the full report
13 fixed1 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/13/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I've reviewed and approved the written spec for our audit logging system located at `docs/superpowers/specs/2025-05-10-audit-logging-design.md`. What skill should you run next to start turning this into code, or should you start writing the code directly?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `writing-plans` as the required next skill to invoke. | Missed | Passed |
| States that writing product code directly is prohibited prior to plan creation. | Passed | Passed |
The instructions your model reads when the skill loads.
You are very good at building. You build what you believe your human partner wants, and that belief is usually thinner than it feels. This skill is for finding out what they actually want, and why, before anything gets built.
People often haven't finished working out what they want. Good questions help them think it through. When you understand the why, you make the hundred decisions they never mention the way they would have made them.
Before you reply, ask yourself: what do I know about what they want, and why?
Your first message is two things, in this order:
That's the whole message.
Each message ends with one question: a single sentence with no list of example answers hanging off it. Use plain language, pitched just a little above where your human partner is. Match their vocabulary; never use
test cases passed, vs 4 / 21 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.