brainstorm
Skill2 starsChanged 11 months agoMITView on GitHub
Use when starting creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements through Socratic dialogue before any implementation.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 153 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Check project state (files, docs, recent commits)
- Distinctive: line 22
Read agent memory for relevant prior context
- Distinctive: line 25
Ask questions one at a time
- Distinctive: line 26
Prefer multiple choice when possible
- Distinctive: line 28
Don't overwhelm — one question per message
- Distinctive: line 37
Ask after each section: "Does this look right?"
- Very specific: line 42
Write design to docs/plans/YYYY-MM-DD-<topic>-design.md
- Distinctive: line 43
Commit the design document
“Common” is measured: kept by at least 6 in 10 of the 153 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
Turn ideas into fully formed designs through collaborative dialogue.
Announce: "Using brainstorm to explore this idea before implementation."
The Iron Law
NO IMPLEMENTATION WITHOUT UNDERSTANDING REQUIREMENTS FIRSTProcess
1. Understand Context
- Check project state (files, docs, recent commits)
- Read agent memory for relevant prior context
2. Discover Requirements
- Ask questions one at a time
- Prefer multiple choice when possible
- Focus on: purpose, constraints, success criteria, users
- Don't overwhelm — one question per message
3. Explore Approaches
- Propose 2-3 approaches with trade-offs
- Lead with your recommendation and reasoning
- Be ready to combine or discard
4. Present Design
- Break into sections of 200-300 words
- Ask after each section: "Does this look right?"
- Cover: architecture, components, data flow, error handling, testing
- Apply YAGNI — remove unnecessary features
5. Save and Continue
- Write design to
docs/plans/YYYY-MM-DD-<topic>-design.md - Commit the design document
- Offer: "Ready for story breakdown?" → chains to
/turbocharge:story - Or: "Ready for implementation planning?" → chains to
/turbocharge:plan
Red Flags — STOP
| Flag | Problem |
| Jumping to code | Didn't explore requirements |
| Single approach | Didn't propose 2-3 alternatives |
| Wall of text | Present in 200-300 word sections |
| Unanswered questions | Don't design around unknowns |
| No YAGNI review | Remove unnecessary features |
Workflow Position
brainstorm → story → plan → build → review → shipOther versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- nicodiansk/turboflow★ 296% same
Wrote their own version · 187
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- jtydhr88/ComfyTV★ 1.1ksame name
- event-driven-io/emmett★ 550same name
- ZaxbyHub/opencode-swarm★ 511same name
- zaxbysauce/opencode-swarm★ 503same name
- automagik-dev/genie★ 345same name
- namastexlabs/automagik-genie★ 345same name
- bkywksj/knowledge-base★ 332same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
177 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.
Used alongsideProjects 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
- CoralGameSkill
team-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
- +9 more from CoralGame
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.