brainstorming
Skill112 starsChanged 2 months agoMITView on GitHub
Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.
190 other projects use a version of this.
Adopted by
Most recently taken up by
- DemonDamon/AgenticXtheir own version, first seen Nov 9, 2026
- roundpilot/superpowers-antigravitytheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions 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.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +2 more from Leodorareluctant259
- +6 more from ryanportfolio
Other versions190 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 190
- obra/superpowers★ 314ksame name
- jnMetaCode/superpowers-zh★ 8.4ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- JetBrains/thinkrail★ 7.9ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- microsoft/FluidFramework★ 4.9ksame name
- BetterTyped/react-zoom-pan-pinch★ 1.9ksame name
- lingyired/status-trio★ 1.8ksame name
180 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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aesthetic-instrumentSkill
- anti-patternsSkill
- anydesignSkill
- archetype-review-baseSkill
- build-speedSkill
- codex-hostSkill
- committed-aestheticSkill
- cost-modelSkill
- crystallizeSkill
- decision-evalSkill
- deploy-landedSkill
- discoverySkill
- done-blockedSkill
- great_ctoSkill
- lifecycle-messagingSkill
- migration-ready-schemaSkill
- observability-baselineSkill
- opportunity-solution-treeSkill
- outcome-roadmapSkill
- pm-planningSkill
- pre-mortemSkill
- product-economicsSkill
- prose-styleSkill
- quant-validationSkill
- secrets-rotationSkill
- signing-preflightSkill
- skeptical-triageSkill
- stack-baselineSkill
- test-strategySkill
- ui-ux-pro-maxSkill
- vertical-onboardingSkill
- verticalsSkill
- well-architectedSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 69
If all four agree in Round 1, the framing was too soft — re-run with a sharper, explicitly contrarian Skeptic ("assume this is a bad idea.
“Common” is measured: kept by at least 6 in 10 of the 170 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
brainstorming
Idea work has three movements: diverge → debate → converge. Most teams skip the middle one and converge on the first plausible idea. The debate panel is the point of this skill.
1. Diverge — generate genuinely different bets
From a framed problem (who · cost-of-pain · why-now · success metric), produce 3–5 distinct approaches — different bets, not cosmetic variants. Force diversity along at least one axis each:
- different user (who you serve first)
- different wedge (the one feature you lead with)
- different scope (concierge/manual vs full self-serve)
- different business shape (tool you sell vs outcome you deliver)
For each: the core bet · the smallest version that tests it · the main risk. Reject near-duplicates — if two options share the same bet, drop one and push for a more contrarian alternative.
2. Debate — the idea-debate panel
Four personas, four different models, two rounds. Model diversity matters: different model families fail differently, so they catch different holes.
| Persona | Stance — argues… | Model | Invocation |
| Visionary | the strongest case FOR — the 10x outcome if it works | claude-opus-5 | Task, model: opus |
| Skeptic | the strongest case AGAINST — why it fails / who tried & died | claude-sonnet-5 | Task, model: sonnet |
| User-Advocate | the user's honest reaction — would I pay / switch / care? AND, for any product that messages or collects data from end-recipients, the recipient's consent/opt-in friction (TCPA / opt-out / spam fatigue / who refuses) | claude-haiku-4-5 | Task, model: haiku |
| Pragmatist | cost, time-to-ship, build-vs-buy, unit economics | Kimi K2 | mcp__great_cto_llm_router__ask_kimi |
Round 1 — opening positions (blind, parallel)
Spawn the three Task personas in one message (parallel) + call the Kimi
router for the Pragmatist. Each gets the framed problem + the diverge options and
only its own stance. Prompt template:
You are the {persona} on a product debate panel. Stance: {stance}. Problem: {framing}. Options on the table: {options}. Make the strongest possible {for/against} case. Be specific and concrete — name the mechanism, the comparable, the number. End with: verdict (BUILD / DON'T / PIVOT-to-which-option) + your single biggest worry.
Round 2 — rebuttal (informed)
Feed each persona the other three's Round-1 positions. Ask:
Here are the other panelists' positions: {r1_others}. Rebut the one you most disagree with. Then give your updated verdict and the one condition that would change your mind.
Convergence guard
If all four agree in Round 1, the framing was too soft — re-run with a sharper, explicitly contrarian Skeptic ("assume this is a bad idea; prove it"). Genuine consensus only counts when the Skeptic was given every chance to kill it.
3. Converge — synthesize (the chair decides)
The product-owner (Opus) is the chair, not a vote-counter. Read all eight statements and produce:
- The decisive consideration — the one argument that actually settles it
- Strongest FOR and strongest AGAINST (steelmanned, attributed)
- The call — BUILD / DON'T BUILD / PIVOT, with the reason in one sentence
- What would flip it — the kill-criteria / the condition to revisit
- Dissent preserved — if a persona held a strong minority view, record it; don't launder it out. Tomorrow's "why didn't we think of X" lives here.
Feed this straight into the product brief's Debate digest section.
Cost note
The panel is ~$0.30–0.60 per idea (one Opus + one Sonnet + one Haiku + one Kimi call × 2 rounds). That is the cheapest insurance in the pipeline: it runs before any engineering time is spent, at the stage where "no" is free and "yes" is expensive.
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.

