brainstorm
Skill1 starsChanged 2 months agoMITView on GitHub
選択肢を広げたいとき、「ブレストして」「アイディア出しして」と言われたときに必ず使う。
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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adrSkill
- architecture-checkSkill
- branch-namingSkill
- codex-delegateSkill
- config-explainSkill
- config-setSkill
- cross-reviewSkill
- design-interviewSkill
- diagnosing-bugsSkill
- fix-ciSkill
- handoffSkill
- leakage-checkSkill
- literature-reviewSkill
- mlflow-logSkill
- multi-seedSkill
- mutation-testSkill
- paper-writingSkill
- pre-mortemSkill
- property-testSkill
- python-standardsSkill
- refactor-scoutSkill
- regression-suiteSkill
- retrospectiveSkill
- security-reviewSkill
- spec-checklistSkill
- tddSkill
The file
Files
アイディア出し(発散)
結論を急がず、まず選択肢を広げることに専念する。絞り込みは design-interview など別のステップに任せる。
進め方
1. お題を確認する
何についてのアイディア出しか、1行で確認する。曖昧なら最大1つだけ 確認質問をする。それ以上聞かず、分かる範囲で発散を始める。
2. 発散フェーズ(質を評価せず、量を出す)
以下の複数の視点から、思いつく限り挙げる。この段階では良し悪しを 判断しない。
- 前提を疑う: 当たり前とされている制約を外したらどうなるか
- 類推: 他分野・他プロジェクトで似た問題がどう解かれているか
- 逆転: 「絶対に失敗する方法」を考え、それを反転させる
- 組み合わせ: 既存の要素A・Bを掛け合わせたらどうなるか
- 極端化: 制約を極端に強くする/緩めるとどうなるか
出す数の目安は10〜15個。似たものを削らず、まずは並べる。
3. 整理フェーズ
出したアイディアを3〜5個のグループに分類し、それぞれに短いラベルを つける(例:「データ拡張系」「モデル構造の変更系」「評価指標の見直し系」)。
4. 軽い評価(絞り込みはしない)
各グループについて、以下の観点を簡潔な表で示す。ただし、ここで 「これがおすすめ」と決めつけない。ユーザーが選ぶための材料を渡すだけ。
| 観点 | 意味 |
| 新規性 | どれくらい新しい切り口か |
| 実現性 | 今の環境・スキルで着手しやすいか |
| インパクト | 当たった場合の効果の大きさ |
| 検証しやすさ | 良し悪しを確かめるのにどれくらい時間がかかるか |
5. 保存
ideas/ 配下に保存する(プロジェクト固有の話なら該当プロジェクトの
docs/drafts/ でもよいが、まだプロジェクトが定まっていない段階のアイデアは
ideas/ に置く)。ファイル名は ideas/YYYYMMDD-<お題>-v1.md
(既存の命名慣習、例: ideas/研究アイディア/ がある場合はそちらに合わせる)。
6. 次のステップの提示
ユーザーが方向性を1つ選んだら、design-interview スキルでその案を 深掘りして固めることを提案する。まだ選ばなくてよい場合は、そのまま 保存して終える。
注意
- この段階で「どれが一番良いか」を代わりに決めない。判断材料を渡すことに徹する。
- アイデアの数を絞ろうとしない。多様性を優先する。
- ML/コードに限らず、論文の論理構成、実験の切り口、スライドの見せ方など、 意思決定が必要な話題全般に使ってよい。
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.

