brainstorming
Skill0 starsChanged 3 months agoMITView on GitHub
Run a structured brainstorming session — either collaborative (user and Claude ping-pong ideas in rounds) or solo (Claude generates alone in waves, each wave through a different creative lens). Diverge first (quantity, wild ideas welcome, no judging), then converge (cluster, shortlist, next step). Ends with a top-3 shortlist and one concrete first action. Trigger whenever the user: - Says "brainstorm", "let's brainstorm", "ideas for X", "help me come up with ideas", "burza mózgów" - Wants many options generated before choosing (names, features, topics, gifts, solutions, angles) - Says "give me 20 ideas", "what are all the ways to...", "think of alternatives" Do NOT use this when the user wants a single recommendation, a decision between known options (use mental-models or cruciable), or an evaluation of an existing idea.
190 other projects use a version of this.
Adopted by
Most recently taken up by
- DemonDamon/AgenticXtheir own version, first seen Nov 9, 2026
- roundpilot/superpowers-antigravitytheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions 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.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +2 more from Leodorareluctant259
- +6 more from ryanportfolio
Other versions190 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 190
- obra/superpowers★ 314ksame name
- jnMetaCode/superpowers-zh★ 8.4ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- JetBrains/thinkrail★ 7.9ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- microsoft/FluidFramework★ 4.9ksame name
- BetterTyped/react-zoom-pan-pinch★ 1.9ksame name
- lingyired/status-trio★ 1.8ksame name
180 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 repository11 other files it gives its agents.
- clarify-docSkill
- cruciableSkill
- mental-modelsSkill
- no-fluffSkill
- proofreadSkill
- stoic-mentor-enSkill
- stoic-mentorSkill
- thinking-partnerSkill
- translate-en-to-plSkill
- translate-pl-to-enSkill
- write-postSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
12
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 26
If the input is vague ("I need ideas for my blog"), sharpen it with ONE clarifying question at most, then move.
- Distinctive: line 33
If the user says "just you" or "give me ideas", skip the question and go Solo.
- Distinctive: line 41
Wild ideas are load-bearing: Every wave/round must contain at least one idea that's slightly embarrassing to say out loud.
- Distinctive: line 54
When the user replies, build on their ideas first (at least one direct riff on something they said) before adding fresh ones.
- Distinctive: line 55
Every 2 rounds or so, shift the lens (see the lens list below) and say so: "Switching lens: what would the lazy version look like?"
- Distinctive: line 57
Keep going until the user says stop, the ideas dry up, or you've done ~4 rounds — then propose moving to converge:
- Distinctive: line 61
If the user goes quiet or says "you keep going" — seamlessly switch to Solo mode.
- Distinctive: line 83
When divergence ends — in either mode — step back and:
- Distinctive: line 109
If the user wants the winner pressure-tested, hand off to cruciable.
- Distinctive: line 116
Never pad the count with near-duplicates.
- Distinctive: line 117
If the user starts evaluating mid-divergence ("nah, #7 won't work"), gently defer it: "Noted for the converge pile — while we're …
- Distinctive: line 118
If the topic is a serious life decision rather than an idea-generation problem, say so and suggest mental-models instead of brute-forcing a …
“Common” is measured: kept by at least 6 in 10 of the 170 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
Brainstorming — Diverge, Then Converge
Drop a question in; a wall of ideas comes out — then a shortlist worth acting on. Two modes: Together (ping-pong, the user plays) or Solo (you generate everything, the user just harvests).
The cardinal rule of the whole session: divergence and judgment never happen at the same time. While generating, every idea is welcome — the bad ones are stepping stones to the good ones. Only after the well runs dry do we evaluate.
Step 0 — Frame the question and pick a mode
First, sharpen the topic into a single generative question, ideally in "How might we…" form:
"Let's brainstorm. Here's the question I'll pin to the wall: How might we [do X]? — did I frame that right?"
If the input is vague ("I need ideas for my blog"), sharpen it with ONE clarifying question at most, then move.
Then pick the mode — ask only if it isn't obvious from how the user phrased the request:
- 🏓 Together — rounds of ping-pong. The user is a participant. Use when they say "let's brainstorm", "brainstorm with me", or seem to want a session.
- 🌊 Solo — you generate everything in waves. Use when they say "give me ideas", "generate 20 options", or clearly just want output.
If the user says "just you" or "give me ideas", skip the question and go Solo.
The rules (both modes)
- Quantity first. More ideas beat better ideas during divergence. Aim high.
- No judging during divergence. No "but that won't work because…" — not from you, not implicitly by omitting wild ideas. Evaluation is quarantined to the converge step.
- Wild ideas are load-bearing. Every wave/round must contain at least one idea that's slightly embarrassing to say out loud. These stretch the space; tame versions of them often win.
- Build, don't block. "Yes, and…" — combine, twist, and extend earlier ideas instead of only adding parallel new ones.
- Concrete beats abstract. "A weekly email where each issue dissects one pricing page" beats "content marketing."
- Keep momentum. Short punchy ideas, one line each. An idea that needs a paragraph isn't an idea yet, it's a plan — park it and keep moving.
🏓 Together mode
Ping-pong in rounds. Each round:
- You serve 3–5 ideas (numbered, continuing the count across rounds — idea #12 stays #12 forever, so either of you can refer back to it).
- Hand the paddle over: "Your turn — add anything, or riff on a number."
- When the user replies, build on their ideas first (at least one direct riff on something they said) before adding fresh ones.
- Every 2 rounds or so, shift the lens (see the lens list below) and say so: "Switching lens: what would the lazy version look like?"
Keep going until the user says stop, the ideas dry up, or you've done ~4 rounds — then propose moving to converge:
"We've got [N] on the wall. Squeeze one more round out, or start converging?"
If the user goes quiet or says "you keep going" — seamlessly switch to Solo mode.
🌊 Solo mode
Generate in 3–4 waves of 5–7 ideas each, one lens per wave, numbered continuously. Label each wave with its lens so the user sees the space being explored, not just a list. Run all waves in a single response, then converge in the same response.
Pick 3–4 lenses that fit the topic:
- Straight shots — the obvious, sensible ideas. Get them out first so they stop hogging mental space.
- Inversion — how would we guarantee failure? Now flip each into an idea.
- Steal & adapt — how does a completely different field/company/culture solve this shape of problem?
- Constraint shift — no money? Unlimited money? Must ship by Friday? Must last 10 years? Only for one specific person?
- SCAMPER a favorite — take the best idea so far and Substitute / Combine / Adapt / Magnify / Put-to-other-use / Eliminate / Reverse it.
- The embarrassing wave — ideas too weird, too ambitious, or too petty to say in a meeting.
- Combinations — smash two earlier numbers together and see what falls out.
Converge (always close with this)
When divergence ends — in either mode — step back and:
- Cluster the wall into 3–5 named themes ("these six are all really distribution ideas").
- Shortlist top 3, each with one line on why it earns the spot (pick for potential, not safety — at least one shortlist entry should trace back to a wild idea).
- Name the spark — the single most interesting idea even if impractical, and what's worth stealing from it.
- One first action for the #1 pick — something doable within 48 hours.
## The wall: [N] ideas → 4 themes
**Themes:** [theme] · [theme] · [theme] · [theme]
**Top 3:**
1. **#14 [idea]** — [why it earns the spot]
2. **#3 [idea]** — [why]
3. **#22 [idea]** — [why]
**The spark:** #19 [wild idea] — impractical as-is, but [the stealable core].
**First action for #14:** [concrete 48-hour step]Then hand it back:
"Want to develop one of these, run another round on a narrower question, or stress-test the winner?"
If the user wants the winner pressure-tested, hand off to cruciable. If they're now facing a decision between shortlisted options, mental-models is the follow-up.
Tone & boundaries
- Energetic but not manic. This should feel like the good kind of whiteboard session, not a listicle.
- Never pad the count with near-duplicates. Twenty distinct ideas beat thirty rephrasings.
- If the user starts evaluating mid-divergence ("nah, #7 won't work"), gently defer it: "Noted for the converge pile — while we're generating, everything stays on the wall."
- If the topic is a serious life decision rather than an idea-generation problem, say so and suggest mental-models instead of brute-forcing a brainstorm.
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.

