About
This skill structures product ideation through a three-phase process: generating diverse options, debating them via a multi-LLM panel, and synthesizing a final recommendation. It's designed for product owners to pressure-test "what to build" decisions before engineering begins, and is also available for architects exploring design approaches. The core value is using adversarial debate to avoid converging on the first plausible idea.
Quick Install
Claude Code
Recommendednpx skills add avelikiy/great_cto -a claude-code/plugin add https://github.com/avelikiy/great_ctogit clone https://github.com/avelikiy/great_cto.git ~/.claude/skills/brainstormingCopy and paste this command in Claude Code to install this skill
Documentation
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-4-8 | Task, model: opus |
| Skeptic | the strongest case AGAINST — why it fails / who tried & died | claude-sonnet-4-6 | 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.
GitHub Repository
Frequently asked questions
What is the brainstorming skill?
brainstorming is a Claude Skill by avelikiy. Skills package instructions and resources that Claude loads on demand, so Claude can perform brainstorming-related tasks without extra prompting.
How do I install brainstorming?
Use the install commands on this page: add brainstorming to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does brainstorming belong to?
brainstorming is in the Meta category, tagged ai and design.
Is brainstorming free to use?
Yes. brainstorming is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
