avelikiy/great_cto / skills/brainstorming
brainstorming
VerifiedStructured 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.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |