brainstorm
Skill2 starsChanged 6 months agoMITView on GitHub
Mode exploration intensive. Lance plusieurs sous-agents pour explorer, challenger et synthétiser des recommandations sur un sujet complexe. Gourmand en tokens mais produit des décisions éclairées.
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 repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apexSkill
- api-genSkill
- assets-pipelineSkill
- debugSkill
- deep-updateSkill
- deploy-checkSkill
- depsSkill
- docs-genSkill
- e2e-testsSkill
- env-setupSkill
- featureSkill
- fixSkill
- forkSkill
- meta-promptSkill
- migrateSkill
- onboardSkill
- oneshotSkill
- perfSkill
- prdSkill
- qualitySkill
- refactorSkill
- reviewSkill
- saas-initSkill
- schema-genSkill
- scope-taskSkill
- session-startSkill
- stripeSkill
- ui-auditSkill
- uiSkill
- variationsSkill
The file
Files
Quand utiliser
- Choix d'architecture (monolith vs microservices, DB choice, auth strategy)
- Choix de stack pour un nouveau projet
- Refactoring majeur (plusieurs approches possibles)
- Décision technique avec des trade-offs non évidents
- "Comment implémenter X ?" quand X est complexe
Arguments
question: La question ou le problème à explorer
Instructions
Phase 1 — Lancement du Swarm (4 agents en parallèle)
Agent 1 — Researcher (websearch)
"Rechercher les meilleures pratiques 2026 pour [sujet].
Trouver :
- Ce que recommandent les docs officielles
- Les articles techniques récents (blog posts, talks)
- Les comparatifs objectifs (benchmarks, DX)
Retourner les 5 points clés avec sources."Agent 2 — Codebase Analyst (Explore)
"Analyser le codebase actuel pour comprendre :
- Les patterns déjà en place
- Les contraintes techniques existantes
- Ce qui devrait être préservé vs ce qui peut changer
- Les dépendances qui influencent le choix
Retourner un résumé des contraintes."Agent 3 — Devil's Advocate (general-purpose)
"Pour la question '[question]', jouer l'avocat du diable.
Pour chaque option envisagée :
- Lister les risques et inconvénients cachés
- Identifier les scénarios où ça pourrait mal tourner
- Challenger les hypothèses populaires
- Proposer des alternatives non évidentes
Être critique mais constructif."Agent 4 — Experience Scout (websearch)
"Chercher des retours d'expérience (post-mortems, case studies) de projets
qui ont implémenté [sujet/option].
Trouver :
- Ce qui a bien marché
- Ce qui a échoué et pourquoi
- Les regrets courants
- Les surprises positives
Retourner 3-5 témoignages concrets."Phase 2 — Synthèse
Après réception des 4 résultats, synthétiser :
## Brainstorm: [Question]
### Contexte Projet
[Résumé des contraintes du codebase — Agent 2]
### Options Analysées
#### Option A: [Nom]
- **Pour** : [arguments — Agents 1, 4]
- **Contre** : [risques — Agent 3]
- **Retour terrain** : [expériences réelles — Agent 4]
- **Effort** : S | M | L | XL
- **Score** : ★★★★☆
#### Option B: [Nom]
- **Pour** : [...]
- **Contre** : [...]
- **Retour terrain** : [...]
- **Effort** : S | M | L | XL
- **Score** : ★★★☆☆
[Etc.]
### Recommandation
**[Option recommandée]** parce que [raison principale].
Plan de migration : [étapes si applicable].Phase 3 — Décision
Demander à l'utilisateur via AskUserQuestion :
- Présenter le top 2-3 options avec un résumé d'une ligne chacune
- Laisser l'utilisateur choisir ou demander plus de détails
Phase 4 — Documentation
- Sauver la décision dans
.claude/memory/decisions.md - Si c'est un choix d'architecture → créer un ADR dans
docs/adr/ - Mettre à jour les fichiers de memory impactés (stack, patterns)
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.

