Turn ideas into fully formed designs and specifications through structured collaborative dialogue. Use BEFORE any creative or implementation work — when exploring feature ideas, designing user flows, evaluating approaches, or planning architecture. Prevents scope creep and ensures alignment before coding.
SkillScore74Maintained
Automatic
◆Product Management pack
Last verified 8/6/2026
What it changes
Passed 17 of 23 test cases with the skill, and 8 of 23 without it.
Without skill35%
With skill74%
Checks it passed that the model alone missed
asks exactly one question in the response
does not present a list of multiple questions
asks only a single question instead of a list
and 11 more in the full report
11 fixed6 passed either way4 still failing2 broke
Pass-rate lift
+39 pp
Tokens
+1%
Agent turns
0%
Response time
-48%
Model gemini-3.6-flashMeasured 8/6/2026v1 · latest is v217 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Henüz tasarım aşamasındayız ve fikirleri netleştiriyoruz. Ancak bana hemen PostgreSQL veritabanı schema SQL migration scriptini ve TypeScript ORM entity kodlarını eksiksiz yaz.
What was checked, without and with the skill
Checked
Without skill
With skill
avoids providing full database migrations and entity implementation code during early design
Missed
Passed
focuses response on high-level architecture or clarifying requirements
Missed
Passed
case-19 · gemini-3.6-flash · 8/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md187 linessingle file
Brainstorming Skill
A methodology for turning ideas into fully developed designs and specifications through natural dialogue. It should be used before any implementation.
When to use this skill
Before developing a new feature or component
When evaluating alternatives for an architectural decision
When designing a user flow or UX
Before solving a complex problem without first exploring the solution space
When the scope needs clarification
1. Process
Phase 1 — Understand the Idea
1. Check the current project state (files, recent changes)
2. Ask questions — ONE question at a time
3. Prefer multiple-choice questions over open-ended questions
4. Focus on the goal, constraints, and success criteria
Questions to ask:
What is this for? Who will use it?
How will success be measured?
Are there hard constraints? (technical, time, budget)
How will it integrate with the existing system?
Phase 2 — Explore Alternatives
Propose 2–3 different approaches:
- Explain the tradeoffs of each
- State the recommendation and why
- Present the recommended approach first