brainstorm
Skill1 starsChanged 6 months agoMITView on GitHub
Orchestrated planning workflow — guides through discovery, PRD creation, vertical-slice phasing, and GitHub issue generation. Use when starting a new project or feature from scratch.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- nielsmadan/skillstheir own version, first seen Nov 8, 2026
- phuthuycoding/kanban-flowtheir own version, first seen Nov 8, 2026
- baethon/skillstheir own version, first seen Nov 8, 2026
- CloudChef/atlasclaw-providerstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- LongJohnSilver1504/claude-skillstheir own version, first seen Nov 8, 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
- 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
- lilangMaxSkill
team-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★ 27ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- jtydhr88/ComfyTV★ 1.2ksame name
- event-driven-io/emmett★ 562same name
- zaxbysauce/opencode-swarm★ 519same name
- ZaxbyHub/opencode-swarm★ 518same name
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- bkywksj/knowledge-base★ 340same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same 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 repository13 other files it gives its agents.
- agent-cliSkill
- askSkill
- blueprintSkill
- carveSkill
- dispatchSkill
- handoffSkill
- improve-claude-mdSkill
- leanSkill
- llm-councilSkill
- orientSkill
- react-auditSkill
- shipSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
2
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
- Very specific: line 12
If $ARGUMENTS contains an idea description, use it as the starting context.
- Distinctive: line 18
Run a discovery interview to pressure-test the idea.
- Distinctive: line 56
Before moving to the next phase:
“Common” is measured: kept by at least 6 in 10 of the 156 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 — Full Workflow
Guide the client through the complete brainstormer workflow, from rough idea to dev-ready GitHub issues. This is the recommended entry point for new engagements.
Getting Started
If $ARGUMENTS contains an idea description, use it as the starting context. Otherwise, ask the client to describe their idea.
Workflow Phases
Phase 1: Discovery (/ask)
Run a discovery interview to pressure-test the idea. Cover:
- Problem and target users
- Business model and constraints
- Scale and operations
- Domain-specific concerns
Do not advance until the client confirms the discovery summary is complete.
Phase 2: Requirements (/blueprint)
Formalize the discovery output into a Product Requirements Document:
- Interview for remaining details
- Sketch system components
- Submit the PRD as a GitHub issue
Do not advance until the PRD issue is created and the client approves it.
Phase 3: Planning (/carve)
Break the PRD into tracer-bullet vertical slices:
- Identify durable architectural decisions
- Draft phases as thin end-to-end slices
- Save the plan to
./plans/
Do not advance until the client approves the phase breakdown.
Phase 4: Issues (/dispatch)
Convert the plan into dependency-ordered GitHub issues:
- Each issue is a vertical slice classified as AFK or HITL
- Created in dependency order with blocker links
After Completion (optional)
Once all issues are created, suggest /improve-claude-md if the target project has a CLAUDE.md that could benefit from optimization.
Phase Transitions
Before moving to the next phase:
- Summarize what was accomplished in the current phase
- Confirm the client is ready to proceed
- Mention that
/leanis available at any point to check for over-engineering - Mention that
/llm-councilis available for any strategic decision where the client wants multi-perspective analysis
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.