Guide for structured exploration of ideas through Socratic questioning.
When to Use
Exploring new feature ideas or requirements
Evaluating multiple solution approaches
Challenging assumptions about a problem
Breaking down complex decisions
Early-stage design discussions
Socratic Questioning Framework
1. Clarifying Questions
What do you mean by...?
What is the core problem we're solving?
Can you give an example?
What would success look like?
2. Probing Assumptions
What are we assuming here?
Why do we believe this is true?
What if the opposite were true?
What are we taking for granted?
3. Exploring Perspectives
How would [stakeholder] view this?
What would a user expect?
What would a skeptic say?
How have others solved similar problems?
4. Examining Evidence
What evidence supports this approach?
Are there counter-examples?
What data would change our mind?
How confident are we in this?
5. Considering Consequences
What happens if we do this?
What are the second-order effects?
What could go wrong?
What's the cost of being wrong?
6. Questioning the Question
Is this the right question to ask?
What question should we be asking instead?
Are we solving the right problem?
Brainstorming Session Structure
1. DEFINE (5 min)
- State the problem/opportunity clearly
- Identify constraints and goals
2. DIVERGE (15 min)
- Generate many ideas without judgment
- Build on each other's ideas
- Encourage wild ideas
3. CHALLENGE (10 min)
- Apply Socratic questions to top ideas
- Identify hidden assumptions
- Explore edge cases
4. CONVERGE (10 min)
- Evaluate ideas against criteria
- Combine complementary approaches
- Select promising directions
5. NEXT STEPS (5 min)
- Define concrete actions
- Assign owners and timelines
Project-Specific Context
[CUSTOMIZE] Add domain-specific questions relevant to your project:
Industry-specific considerations
Technical constraints unique to your stack
Stakeholder perspectives to consider
Common assumptions in your domain
Output Artifacts
After brainstorming, document:
Problem statement (refined)
Key insights discovered
Assumptions identified (and which were challenged)
Top approaches with pros/cons
Decision and rationale
Open questions for future exploration
Gotchas
Trigger
Gotcha
Fix
"This approach seems good" in the first few minutes
Premature convergence — first idea is never fully examined
Enforce a DIVERGE phase before CONVERGE; exhaust alternatives before committing
Everyone agrees quickly with no pushback
Groupthink — consensus silences better options
Assign devil's advocate; use §2 Probing Assumptions questions to challenge the consensus
30+ minutes of questioning with no decision
Analysis paralysis — endless questioning without converging
Time-box phases using the Session Structure; reach CONVERGE by minute 30
Questions framed as "Shouldn't we use X?"
Leading questions — forecloses alternatives before exploration
Rephrase as open questions per §1 Clarifying format ("What are the options here?")
Socratic questions met with defensiveness
Defensive responses — posture shuts down exploration
Frame questions as discovery, not criticism; restate the exploration goal
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: grimblaz-workflow-template-brainstorming3description: Brainstorming Skill4---56# Brainstorming Skill78Guide for structured exploration of ideas through Socratic questioning.910## When to Use1112- Exploring new feature ideas or requirements13- Evaluating multiple solution approaches14- Challenging assumptions about a problem15- Breaking down complex decisions16- Early-stage design discussions1718## Socratic Questioning Framework1920### 1. Clarifying Questions2122- What do you mean by...?23- What is the core problem we're solving?24- Can you give an example?25- What would success look like?2627### 2. Probing Assumptions2829- What are we assuming here?30- Why do we believe this is true?31- What if the opposite were true?32- What are we taking for granted?3334### 3. Exploring Perspectives3536- How would [stakeholder] view this?37- What would a user expect?38- What would a skeptic say?39- How have others solved similar problems?4041### 4. Examining Evidence4243- What evidence supports this approach?44- Are there counter-examples?45- What data would change our mind?46- How confident are we in this?4748### 5. Considering Consequences4950- What happens if we do this?51- What are the second-order effects?52- What could go wrong?53- What's the cost of being wrong?5455### 6. Questioning the Question5657- Is this the right question to ask?58- What question should we be asking instead?59- Are we solving the right problem?6061## Brainstorming Session Structure6263```641. DEFINE (5 min)65 - State the problem/opportunity clearly66 - Identify constraints and goals67682. DIVERGE (15 min)69 - Generate many ideas without judgment70 - Build on each other's ideas71 - Encourage wild ideas72733. CHALLENGE (10 min)74 - Apply Socratic questions to top ideas75 - Identify hidden assumptions76 - Explore edge cases77784. CONVERGE (10 min)79 - Evaluate ideas against criteria80 - Combine complementary approaches81 - Select promising directions82835. NEXT STEPS (5 min)84 - Define concrete actions85 - Assign owners and timelines86```8788## Project-Specific Context8990[CUSTOMIZE] Add domain-specific questions relevant to your project:9192- Industry-specific considerations93- Technical constraints unique to your stack94- Stakeholder perspectives to consider95- Common assumptions in your domain9697## Output Artifacts9899After brainstorming, document:1001011. Problem statement (refined)1022. Key insights discovered1033. Assumptions identified (and which were challenged)1044. Top approaches with pros/cons1055. Decision and rationale1066. Open questions for future exploration107108## Gotchas109110| Trigger | Gotcha | Fix |111| --------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |112| "This approach seems good" in the first few minutes | Premature convergence — first idea is never fully examined | Enforce a DIVERGE phase before CONVERGE; exhaust alternatives before committing |113| Everyone agrees quickly with no pushback | Groupthink — consensus silences better options | Assign devil's advocate; use §2 Probing Assumptions questions to challenge the consensus |114| 30+ minutes of questioning with no decision | Analysis paralysis — endless questioning without converging | Time-box phases using the Session Structure; reach CONVERGE by minute 30 |115| Questions framed as "Shouldn't we use X?" | Leading questions — forecloses alternatives before exploration | Rephrase as open questions per §1 Clarifying format ("What are the options here?") |116| Socratic questions met with defensiveness | Defensive responses — posture shuts down exploration | Frame questions as discovery, not criticism; restate the exploration goal |117118---119> Converted and distributed by [TomeVault](https://tomevault.io/claim/grimblaz) — claim your Tome and manage your conversions.120<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/grimblaz-workflow-template-brainstorming in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Brainstorming Skill It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io