This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning.
SkillScore68Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 15 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill68%
Checks it passed that the model alone missed
Directs the user to run /workflows:plan as the next action
Limits the main feature description section to a maximum of 2 paragraphs
Includes a frontmatter block containing metadata fields for date and topic
and 7 more in the full report
8 fixed7 passed either way3 still failing4 broke
Pass-rate lift
+18 pp
Tokens
+6%
Agent turns
0%
Response time
-58%
Model gemini-3.6-flashMeasured 8/19/2026v115 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We have chosen our approach for the search filtering feature on topic 'catalog-search' for today's date 2026-03-30. Where should the design summary document be stored, and what file path should be used?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies the output path docs/brainstorms/2026-03-30-catalog-search-brainstorm.md
Missed
Passed
case-14 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md185 linessingle file
Brainstorming
This skill provides detailed process knowledge for effective brainstorming sessions that clarify WHAT to build before diving into HOW to build it.
When to Use This Skill
Brainstorming is valuable when:
Requirements are unclear or ambiguous
Multiple approaches could solve the problem
Trade-offs need to be explored with the user
The user hasn't fully articulated what they want
The feature scope needs refinement
Brainstorming can be skipped when:
Requirements are explicit and detailed
The user knows exactly what they want
The task is a straightforward bug fix or well-defined change
Core Process
Phase 0: Assess Requirement Clarity
Before diving into questions, assess whether brainstorming is needed.
Signals that requirements are clear:
User provided specific acceptance criteria
User referenced existing patterns to follow
User described exact behavior expected
Scope is constrained and well-defined
Signals that brainstorming is needed:
User used vague terms ("make it better", "add something like")
Multiple reasonable interpretations exist
Trade-offs haven't been discussed
User seems unsure about the approach
If requirements are clear, suggest: "Your requirements seem clear. Consider proceeding directly to planning or implementation."