Skip to content
Development
Skill

/brainstorming

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

From plugin
great-cto
11333 skills72 agents21 commands1 hook

Claude Code

$ npx -y skills add avelikiy/great_cto --skill brainstorming --agent claude-code

SKILL.md

brainstorming.SKILL.md
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.

Read more
@avelikiy
Ships withgreat-cto

You already have the agent. This is everything around it. great_cto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.

11333 skills72 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
113
Star history of avelikiy/great_cto on GitHub, a chart by star-history.com

Other skills on great-cto.

aesthetic-instrument

aesthetic-instrument

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided…

@avelikiy@avelikiyInstall Skill
anti-patterns

anti-patterns

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or…

@avelikiy@avelikiyInstall Skill
anydesign

anydesign

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component…

@avelikiy@avelikiyInstall Skill
archetype-review-base

archetype-review-base

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the…

@avelikiy@avelikiyInstall Skill
codex-host

codex-host

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact…

@avelikiy@avelikiyInstall Skill
committed-aesthetic

committed-aesthetic

How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick,…

@avelikiy@avelikiyInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc12d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about brainstorming.

Which coding agents can use brainstorming?
brainstorming installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.