brainstorming · avelikiy — Claude Code skill: ideas, model debate, verdict
Takes a raw product idea through three steps: divergent bets, a two-round argument between four personas on four models, and a synthesised call.
npx skills add avelikiy/great_cto --skill brainstorming -a claude-codeWhat brainstorming does
The skill runs in three movements: diverge, debate, converge. From a framed problem — who, cost of the pain, why now, success metric — it produces 3–5 distinct approaches rather than cosmetic variants. Each one differs on at least one axis: a different user, a different lead feature, a different scope, a different business shape. Every option comes with its core bet, the smallest version that tests it, and the main risk.
The middle movement is the reason the skill exists. Four personas on four models argue for two rounds. Visionary runs on claude-opus-5 via Task and builds the case for; Skeptic on claude-sonnet-5 builds the case against; User-Advocate on claude-haiku-4-5 asks whether anyone would pay or switch; Pragmatist goes to Kimi K2 through mcp__great_cto_llm_router__ask_kimi to weigh cost, time-to-ship and unit economics. Round one is blind — nobody sees the others. Round two hands each persona the other three positions and asks for a rebuttal plus the one condition that would change their mind. If all four agree straight away, the skill suggests re-running with a harsher Skeptic.
The product-owner chairs the synthesis instead of counting votes: the decisive consideration, the strongest case each way, a BUILD / DON'T BUILD / PIVOT call, what would flip it, and any minority view kept on record. A run costs roughly $0.30–0.60, spent before any engineering time.
What it helps with
- pull several genuinely different options out of a raw idea
- pressure-test a concept before engineers spend time on it
- hear an honest user reaction instead of only the author's case
- size cost and time-to-ship before development starts
- record the condition that would reopen the decision
Example prompts for the agent
- Run this idea through brainstorming: diverge the options, hold the panel debate, give me the verdict
- Use the brainstorming skill to pressure-test this concept before the brief
- Work through the brainstorming steps and recommend a call with the condition that would flip it
How to install brainstorming
1Skills CLI (Vercel)
npx skills add avelikiy/great_cto --skill brainstorming -a claude-code2Manually: put the files in place
~/.claude/skills/brainstorming/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brainstorming/
1Skills CLI (Vercel)
npx skills add avelikiy/great_cto --skill brainstorming -a codex2Manually: put the files in place
.agents/skills/brainstorming/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add avelikiy/great_cto --skill brainstorming -a cursor2Manually: put the files in place
.cursor/skills/brainstorming/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install avelikiy/great_cto brainstorming2Manually: put the files in place
.github/skills/brainstorming/SKILL.md1Skills CLI (Vercel)
npx skills add avelikiy/great_cto --skill brainstorming -a gemini-cli2Platform CLI
gemini skills install https://github.com/avelikiy/great_cto --path skills/brainstormingManually: put the files in place
.devin/skills/brainstorming/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add avelikiy/great_cto --skill brainstorming -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about brainstorming
How do I install brainstorming in Claude Code?
Run npx skills add avelikiy/great_cto --skill brainstorming -a claude-code. The skill then lands at ~/.claude/skills/brainstorming/SKILL.md.
What does brainstorming do?
It generates several distinct product bets, puts them through a two-round debate between four personas on four models, and synthesises one recommendation with a revisit condition.
What does the skill need to run?
The great_cto_llm_router MCP server with its ask_kimi tool, which the Pragmatist persona calls.
Source text
SKILL.md · MIT
---
name: brainstorming
description: 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.
when_to_use: |
Apply when:
- product-owner is turning a raw idea/problem into a validated brief
- the decision is "what/whether to build", not "how to build it"
- an idea needs adversarial pressure-testing before committing engineering time
- architect wants to explore a wide design space before picking an approach
effort: medium
allowed-tools: Read, Write, Task, mcp__great_cto_llm_router__ask_kimi
---
# 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.
© avelikiy · MIT · avelikiy/great_cto
Similar skills
All skills for Agent setup: memory, context, orchestration →brainstorming by other authors comes first.