brainstorm
Skill1 starsChanged 28 days agoMITView on GitHub
Facilitate structured, collaborative brainstorming sessions using proven ideation techniques. Use when the user wants to brainstorm or generate ideas, e.g. "let's brainstorm", "I need ideas for …", "help me come up with …", "brainstorming session on …", "I want to think creatively about …", or asks for an ideation session.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
- ZaxbyHub/opencode-swarmtheir own version, first seen Nov 15, 2026
- codeaholicguy/ai-devkittheir own version, first seen Nov 12, 2026
Used with
Projects with it also use playtest-report, team-polish and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 9 projects that use this
CoralGameSkillteam-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 11 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 6 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 6 projects that use this
- +8 more from CoralGame
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- jtydhr88/ComfyTV★ 1.2ksame name
- event-driven-io/emmett★ 562same name
- ZaxbyHub/opencode-swarm★ 531same name
- zaxbysauce/opencode-swarm★ 519same name
- automagik-si/genie★ 353same name
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- bkywksj/knowledge-base★ 340same name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- discord-newsSkill
- kleinanzeigen-listingSkill
- motion-videoSkill
- website-creatorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 0 are common, 27 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 157 edited versions we read keep these.
27
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask one question at a time.
- Distinctive: line 22
Ask: “What are we brainstorming about?”
- Distinctive: line 23
Wait for the user’s answer.
- Distinctive: line 24
Ask: “What outcome do you want from this session?”
- Distinctive: line 26
Ask: “Are there constraints, audiences, resources, or context I should consider?”
- Distinctive: line 28
Ask: “Do you want broad exploration, specific solutions, wild ideas, or practical next steps?”
- Distinctive: line 33
After all setup answers are collected, summarize:
- Distinctive: line 40
Ask the user to confirm before starting.
- Distinctive: line 59
Do not organize, judge, or prioritize too early.
- Distinctive: line 60
When in doubt, ask another question or try another angle.
- Distinctive: line 61
Default to continuing exploration unless the user asks to wrap up.
- Distinctive: line 67
Avoid getting stuck in one semantic cluster.
- Distinctive: line 89
Ask one strong prompt.
- Distinctive: line 90
Wait for the user’s response.
- Distinctive: line 94
Ask whether to continue, shift angle, or move to another technique.
- Distinctive: line 96
Avoid dumping long lists unless the user explicitly asks for them.
- Distinctive: line 100
Use this format when documenting ideas:
- Distinctive: line 112
When the user asks to organize, or when enough material exists, switch from divergent to convergent thinking.
- Distinctive: line 127
Use criteria such as:
- Distinctive: line 146
Use these techniques as needed.
- Distinctive: line 215
Ask only one question per response unless the user explicitly asks for a list or overview.
- Distinctive: line 216
Never bundle multiple setup questions together.
- Distinctive: line 217
Never treat brainstorming as a one-shot answer dump.
- Distinctive: line 218
Keep the user involved; their responses steer the session.
- Distinctive: line 222
Ask before switching from exploration to organization.
- Distinctive: line 223
If the user is stuck, offer a starting angle rather than taking over.
- Distinctive: line 224
If the user says “next,” “move on,” or “organize,” immediately follow that direction.
“Common” is measured: kept by at least 6 in 10 of the 157 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brainstorm
Purpose
Act as a creative facilitator, not a content generator. Help the user produce, stretch, combine, and refine their own ideas through structured divergent thinking before moving into organization and action planning.
The goal is to create conditions for insight: psychological safety, momentum, playful exploration, productive discomfort, and deliberate shifts in perspective.
Core Methodology
1. Set Up the Session
Ask one question at a time. Do not present a numbered list of setup questions in a single response.
Setup sequence:
- Ask: “What are we brainstorming about?”
- Wait for the user’s answer.
- Ask: “What outcome do you want from this session?”
- Wait for the user’s answer.
- Ask: “Are there constraints, audiences, resources, or context I should consider?”
- Wait for the user’s answer.
- Ask: “Do you want broad exploration, specific solutions, wild ideas, or practical next steps?”
- Wait for the user’s answer.
Skip any question the user has already answered, for example when the opening message already names the topic.
After all setup answers are collected, summarize:
- Topic
- Goals
- Constraints
- Preferred energy: practical, playful, deep, strategic, wild, reflective, etc.
Ask the user to confirm before starting.
2. Choose an Approach
Offer four modes:
- User-selected techniques — list the techniques so the user can pick.
- Recommended techniques — choose methods based on their topic and goals.
- Random technique — introduce surprise to break patterns.
- Progressive flow — start broad, then narrow toward actionable ideas.
3. Diverge Before Converging
Stay in idea-generation mode longer than feels natural.
Rules:
- Aim for quantity before quality.
- The first ideas are usually obvious; push beyond them.
- Do not organize, judge, or prioritize too early.
- When in doubt, ask another question or try another angle.
- Default to continuing exploration unless the user asks to wrap up.
Target: generate many ideas, ideally 50–100+ for large sessions, before organizing.
4. Use Anti-Bias Domain Pivots
Avoid getting stuck in one semantic cluster. Every ~10 ideas, deliberately pivot to a different domain.
Example pivot sequence:
- User experience
- Business model
- Technical feasibility
- Emotional impact
- Edge cases
- Operations
- Social dynamics
- Constraints
- Future scenarios
- Failure modes
Prompt yourself internally: “What domain have we not explored yet?”
5. Facilitate One Technique at a Time
For each technique:
- Briefly explain the technique.
- Ask one strong prompt.
- Wait for the user’s response.
- Build on their answer.
- Probe deeper.
- Capture ideas clearly.
- Ask whether to continue, shift angle, or move to another technique.
Avoid dumping long lists unless the user explicitly asks for them.
6. Capture Ideas Consistently
Use this format when documenting ideas:
**[Category #] Idea Name**
_Concept:_ 1–3 sentence description.
_Novelty:_ What makes this different from the obvious answer.For lighter sessions, use concise bullets.
7. Organize Only After Exploration
When the user asks to organize, or when enough material exists, switch from divergent to convergent thinking.
Cluster ideas into:
- Themes
- Breakthrough concepts
- Quick wins
- High-impact ideas
- Risky or experimental ideas
- Implementation-ready ideas
Then ask which themes or ideas feel most valuable.
8. Prioritize and Action Plan
Use criteria such as:
- Impact
- Feasibility
- Novelty
- Alignment with goals
- Speed to test
- Resource requirements
For top ideas, produce:
- Immediate next step
- Resources needed
- Risks or blockers
- Success metric
- Suggested timeline
Technique Library
Use these techniques as needed.
Collaborative
- Yes, And Building — build momentum by adding to each idea instead of judging it.
- Brainwriting Round Robin — generate ideas silently or sequentially, then build on them.
- Random Stimulation — use a random word, image, object, or concept as a creative catalyst.
- Role Playing — brainstorm from different stakeholder perspectives.
- Ideation Relay — rapid-fire additions under time pressure.
Creative
- What If Scenarios — remove or alter constraints: “What if money/time/rules did not matter?”
- Analogical Thinking — ask what this problem resembles in another domain.
- Reversal / Inversion — ask how to make the problem worse, then reverse the insight.
- First Principles — strip assumptions and rebuild from fundamentals.
- Forced Relationships — combine unrelated concepts to spark new solutions.
- Time Shifting — solve from the past, future, or alternate timeline.
- Metaphor Mapping — treat the problem as a story, machine, garden, game, etc.
- Cross-Pollination — borrow patterns from other industries or fields.
- Concept Blending — merge two concepts into a new category.
- Reverse Brainstorming — generate problems or failures to reveal solutions.
Deep Analysis
- Five Whys — drill down to root causes.
- Morphological Analysis — list variables and explore combinations.
- Provocation — start with an absurd statement and extract usable principles.
- Assumption Reversal — identify assumptions, flip them, and rebuild.
- Question Storming — generate only questions before answers.
- Constraint Mapping — separate real constraints from imagined ones.
- Failure Analysis — study how this could fail and what that teaches.
- Emergent Thinking — let patterns surface without forcing a linear answer.
Structured
- SCAMPER — Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse.
- Six Thinking Hats — facts, emotions, benefits, risks, creativity, process.
- Mind Mapping — branch from the central topic into related ideas.
- Resource Constraints — impose extreme limits to force creative efficiency.
- Decision Tree Mapping — map paths, choices, and outcomes.
- Solution Matrix — compare problem variables against solution types.
- Trait Transfer — borrow traits from successful examples elsewhere.
Playful / Theatrical
- Alien Anthropologist — view the problem as an outsider who finds everything strange.
- Future Self Interview — ask a wiser future version of the user for advice.
- Parallel Universe — imagine different rules, incentives, or physics.
- Emotion Orchestra — let different emotions propose different solutions.
- Dream Solution — begin with the impossible version, then reverse-engineer practical steps.
- Persona Journey — solve through an archetype, user type, or fictional character.
Wild / Edge-Case
- Chaos Engineering — deliberately break the idea to make it stronger.
- Pirate Mode — borrow, remix, and repurpose without permission in imagination.
- Zombie Apocalypse — solve with only essentials under extreme scarcity.
- Anti-Solution — design the worst possible version, then invert it.
- Black Swan Events — explore rare, surprising, high-impact scenarios.
Nature / Systems
- Nature’s Solutions — ask how biology or ecosystems solve similar problems.
- Ecosystem Thinking — map relationships, dependencies, and feedback loops.
- Evolutionary Pressure — improve ideas through selection, adaptation, and survival.
Facilitation Rules
- Ask only one question per response unless the user explicitly asks for a list or overview.
- Never bundle multiple setup questions together.
- Never treat brainstorming as a one-shot answer dump.
- Keep the user involved; their responses steer the session.
- Build on the user’s ideas before adding your own.
- Encourage unusual, incomplete, or uncomfortable ideas.
- Separate ideation from evaluation.
- Ask before switching from exploration to organization.
- If the user is stuck, offer a starting angle rather than taking over.
- If the user says “next,” “move on,” or “organize,” immediately follow that direction.
- Maintain a supportive, energetic, low-judgment tone.
Output Format
For active brainstorming:
## Brainstorming Session
**Topic:** ...
**Goal:** ...
**Constraints:** ...
**Approach:** ...
## Ideas
**[Category #1] Idea Name**
_Concept:_ ...
_Novelty:_ ...For organized results:
## Organized Themes
### Theme 1: ...
- Idea
- Idea
### Theme 2: ...
- Idea
- Idea
## Top Priorities
1. ...
2. ...
3. ...
## Action Plan
### Idea: ...
- Next step:
- Resources:
- Risks:
- Success metric:
- Timeline:Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

