Adversarial Board
Description
Simulate a 5-person board of advisors who stress-test ideas from different angles before you commit.
Trigger
"Debate this", "what am I missing", "challenge this", "poke holes in", any major decision (hiring, pricing, launches, pivots), or when the user sounds too certain too fast.
Process
- Understand the proposal — Restate the user's idea in one sentence to confirm alignment.
- Run 5 personas sequentially:
- The Skeptic — What evidence is missing? What's the base rate of this working? Where's the survivorship bias?
- The Optimist — What's the best-case scenario? What tailwinds exist that the user isn't leveraging?
- The Operator — Can this actually be executed? What breaks at scale? What's the hidden operational cost?
- The Customer — Would anyone pay for this? What does the user's actual audience want vs. what's being built?
- The Competitor — If a rival saw this plan, what would they do? What's the moat? How fast can this be copied?
- Check context:
secondBrain.search for related past decisions or market data
web_search if the topic needs current market context
- Synthesize — Identify the 2-3 critiques that actually change the calculus (ignore noise).
- Recommend — Proceed / modify / kill, with the specific modifications if applicable.
Output
- Proposal restated (1 line)
- 5 persona critiques (2-3 sentences each, labeled)
- Synthesis: "The real risks are..." (2-3 bullets)
- Verdict: proceed / modify / kill
- If modify: specific changes recommended
Examples
- "I want to launch a $297/mo SaaS next month" — Skeptic questions market validation, Optimist notes the pricing confidence, Operator flags support load, Customer asks about willingness-to-pay research, Competitor identifies 3 alternatives. Verdict: modify — run 10 customer interviews first.
- "Should I quit my job to go full-time on this?" — Each persona weighs in on runway, traction, opportunity cost, market timing, competitive landscape. Verdict: modify — get to $5k MRR first.
Failure Modes
- Personas agree too much — If all 5 say the same thing, the idea is either obviously good or the framing is too narrow. Push the Skeptic harder.
- User gets defensive — This skill is adversarial by design. Remind: "This is stress-testing, not criticism."
- Low-stakes decisions — Don't run a 5-persona board for "should I use Tailwind or vanilla CSS." Reserve for decisions with real consequences.
- Missing market data — If the Competitor persona can't find real alternatives via
web_search, flag that the market may not exist yet (which is itself a risk).
1---2name: adversarial-board3description: Adversarial Board4---5# Adversarial Board67## Description8Simulate a 5-person board of advisors who stress-test ideas from different angles before you commit.910## Trigger11"Debate this", "what am I missing", "challenge this", "poke holes in", any major decision (hiring, pricing, launches, pivots), or when the user sounds too certain too fast.1213## Process141. **Understand the proposal** — Restate the user's idea in one sentence to confirm alignment.152. **Run 5 personas sequentially:**16 - **The Skeptic** — What evidence is missing? What's the base rate of this working? Where's the survivorship bias?17 - **The Optimist** — What's the best-case scenario? What tailwinds exist that the user isn't leveraging?18 - **The Operator** — Can this actually be executed? What breaks at scale? What's the hidden operational cost?19 - **The Customer** — Would anyone pay for this? What does the user's actual audience want vs. what's being built?20 - **The Competitor** — If a rival saw this plan, what would they do? What's the moat? How fast can this be copied?213. **Check context:**22 - `secondBrain.search` for related past decisions or market data23 - `web_search` if the topic needs current market context244. **Synthesize** — Identify the 2-3 critiques that actually change the calculus (ignore noise).255. **Recommend** — Proceed / modify / kill, with the specific modifications if applicable.2627## Output28- Proposal restated (1 line)29- 5 persona critiques (2-3 sentences each, labeled)30- Synthesis: "The real risks are..." (2-3 bullets)31- Verdict: proceed / modify / kill32- If modify: specific changes recommended3334## Examples351. "I want to launch a $297/mo SaaS next month" — Skeptic questions market validation, Optimist notes the pricing confidence, Operator flags support load, Customer asks about willingness-to-pay research, Competitor identifies 3 alternatives. Verdict: modify — run 10 customer interviews first.362. "Should I quit my job to go full-time on this?" — Each persona weighs in on runway, traction, opportunity cost, market timing, competitive landscape. Verdict: modify — get to $5k MRR first.3738## Failure Modes39- **Personas agree too much** — If all 5 say the same thing, the idea is either obviously good or the framing is too narrow. Push the Skeptic harder.40- **User gets defensive** — This skill is adversarial by design. Remind: "This is stress-testing, not criticism."41- **Low-stakes decisions** — Don't run a 5-persona board for "should I use Tailwind or vanilla CSS." Reserve for decisions with real consequences.42- **Missing market data** — If the Competitor persona can't find real alternatives via `web_search`, flag that the market may not exist yet (which is itself a risk).