brainstorm
Skill1 starsChanged 8 months agoMITView on GitHub
Multi-perspective brainstorming session. Use when the user wants to generate and evaluate ideas on a topic. Triggered by idea generation, brainstorming, "any good ideas?", wanting new solutions, or creative suggestions.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- nshopik/dream-teamtheir own version, first seen Nov 16, 2026
- crysix/skillstheir own version, first seen Nov 15, 2026
- 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
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★ 567same name
- zaxbysauce/opencode-swarm★ 532same name
- ZaxbyHub/opencode-swarm★ 531same name
- automagik-dev/genie★ 353same name
- automagik-si/genie★ 353same name
- namastexlabs/automagik-genie★ 353same name
- bkywksj/knowledge-base★ 346same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- evaluateSkill
- learningSkill
- notebookSkill
- plan-projectSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 157 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If NOTEBOOK_PATH is set, search for past entries related to the user's theme:
- Distinctive: line 28
Read up to 3 matching entries (frontmatter + first 200 characters of body)
- Very specific: line 35
Create a team with the following teammates using their agent definitions from .claude/agents/:
- Distinctive: line 61
After the team completes its discussion, create the final output:
“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 Skill
A workflow that creates an Agent Team of Ideator and Analyst to perform iterative idea divergence and convergence through multi-round discussion.
Workflow
Step 1: Understand the Theme
Accurately understand the theme, challenge, or problem presented by the user. If ambiguous, confirm the following before proceeding:
- Target domain (business, technology, creative, etc.)
- Constraints (budget, timeline, tech stack, etc.)
- Required granularity of deliverables
Step 2: Retrieve Past Notebook Context
If NOTEBOOK_PATH is set, search for past entries related to the user's theme:
- Grep
$NOTEBOOK_PATH/ideas/for keywords from the theme (searching title, tags, and body) - Read up to 3 matching entries (frontmatter + first 200 characters of body)
- Include the retrieved content as context when creating the team
Skip this step if zero matches or NOTEBOOK_PATH is not set.
Step 3: Create Agent Team
Create a team with the following teammates using their agent definitions from .claude/agents/:
Teammates:
ideator— generates creative ideasanalyst— evaluates and challenges ideas
Team instructions:
Theme: [User's theme]
[Past Notebook context if found]
Collaboration protocol:
1. Ideator generates 5-7 ideas with summary, rationale, and impact assessment
2. Analyst evaluates each idea (Feasibility, Impact, Novelty, Risk on 1-5 scale) and provides improvement suggestions
3. Ideator refines weak ideas based on Analyst's feedback, may propose new ideas inspired by the critique
4. Analyst re-evaluates the refined ideas
5. Continue iterating until both agree on a final ranked list (aim for 2-3 rounds)
Rules:
- Output language: Use the language specified by OUTPUT_LANGUAGE env var. If not set, match the user's language (default: English)
- If NOTEBOOK_PATH is set: Ideator saves final ideas to $NOTEBOOK_PATH/ideas/, Analyst saves evaluation to $NOTEBOOK_PATH/reviews/
- Each agent writes its own deliverables with structured frontmatterStep 4: Synthesis & Ranking
After the team completes its discussion, create the final output:
## Brainstorming Results: [Theme]
### Discussion Summary
[Brief description of how ideas evolved through iteration]
### #1: [Idea Name]
- **Overall Score**: X.X / 5.0
- **Summary**: ...
- **Scores**: Feasibility X | Impact X | Novelty X | Risk X
- **Strengths**: ...
- **How it was refined**: ...
### #2: [Idea Name]
...
### #3: [Idea Name]
...
### Other Ideas
- [Idea Name]: Overall Score X.X - [One-line summary]
### Next Steps
- Recommend `/evaluate` for detailed assessment of promising ideas
- Recommend `/plan-project` for turning ideas into projectsOutput Format
Present the following to the user:
- Brief summary of the team discussion and iteration process
- Top 3 ideas in detail (with scores, evaluation, and how they were refined)
- List of remaining ideas
- Next step suggestions
- Notebook save notification if applicable
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.

