Coding & Developmentπ€claudeπuniversal
brainstorming
skills/brainstorming/SKILL.md
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.
Quick Start
Install this SKILL.md
npx skills add https://github.com/avelikiy/great_cto/tree/main/skills/brainstorming---
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.
Repository
103stars
13forks
Details
Related Skills
More coding & development skills you might like
Reticle
Coding & DevelopmentAI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.
π€claudeπuniversal
1.2k
190
View
agentscope-java
Coding & DevelopmentExpert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or Java agent development. Specializes in non-blocking code, tool integration, hooks, pipelines, and production-ready agent applications.
πuniversal
6.0k
1.5k
View
ospec
Coding & DevelopmentDocument-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
β¨geminiπ€claudeπ¬gptπuniversal
396
28
View
misakanet-failure-memory
Coding & Developmentπ A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | https://misakanet.org
π€claudeβ¨οΈcursorπuniversal
424
158
View