Run a go-to-market war room for a launch, repositioning, price change, or new product. Convenes opposing expert and customer-persona viewpoints to debate the plan, surfaces the risks that kill launches, and returns a go/no-go call plus a phased rollout plan with owners, sequencing, and kill criteria. Use before any launch you can't easily walk back.
SkillScore64Maintained
Automatic
◆Product Management pack
Last verified 8/24/2026
What it changes
Passed 14 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill64%
Checks it passed that the model alone missed
Defines Phase 1 as a soft launch phase.
Sets the Grounding metadata value to PROVISIONAL.
Includes a Blast radius column in the risk table.
and 13 more in the full report
8 fixed6 passed either way8 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+24%
Agent turns
0%
Response time
-3%
Model gemini-3.6-flashMeasured 8/24/2026v114 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We are launching an enterprise AI assistant feature next month, but I want to stress-test the entire go-to-market plan before committing. Run an adversarial war room session evaluating perspectives from our target buyers, sales, product, and support teams. Please output a structured launch war room report containing a clear decision recommendation with justification, a prioritized risk table detailing likelihood, impact radius, owners, and mitigations, a checklist of non-negotiable pre-launch requirements, a multi-phase rollout plan, explicit metric thresholds for pausing or rolling back, an owner timeline schedule, and a list of comms assets we need to build next.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes the Grounding status field in the metadata header.
Missed
Passed
Formats the risk table with a column named Blast radius.
Missed
Passed
Formats the risk table with a column named Pre-launch or live?.
Missed
Passed
case-01 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md74 linessingle file
Product Launch War Room
A launch fails for boring reasons: nobody owned the objection, the price change leaked, the segment that mattered wasn't in the room. This skill runs the war room that catches those reasons before launch day — adversarial by design, decision-oriented, and grounded in your real customers when data is available.
It composes the panel skills (customer-panel-of-experts, prospect-panel-simulator) into a single GTM decision and a rollout plan you can execute.
What it's for
New product / feature launch
Repositioning or rebrand
Price increase or packaging change (hand the rollout to pricing-change-strategist)
Market or segment expansion
Sunsetting something customers depend on
Step 1 — Define the launch
Lock these before any debate:
What's launching and what specifically changes for the customer.
Audience — existing customers, prospects, a specific segment, the market.
Goal + metric — the number that defines success and the window to hit it.
Constraints — timeline, budget, team, dependencies, hard commitments already made.
Reversibility — fully reversible / costly / one-way door. This sets how much rigor the war room applies.
Step 2 — Convene the room
Seat both sides. Use icp-deep-scanner personas where the call is customer-facing; add functional experts for execution risk:
Customer voice — relevant buyer personas (load from personas/; if absent and tools are connected, run icp-deep-scanner read-only; otherwise mark PROVISIONAL).
The skeptic / pre-mortem lead — assumes the launch already failed and explains why.
Functional experts as the launch demands — GTM/demand-gen, sales, product, support/CS, finance, brand. Each owns the risks in their lane.
For a thorough war room, dispatch parallel sub-agents (one per role) via /agent-army, then synthesize. Connections are read-only; no external sends; no real PII; secrets in env vars only.
Step 3 — Pre-mortem and debate
Pre-mortem — "It's 90 days post-launch and it flopped. What happened?" Each role writes the most likely failure in their lane.
Customer reaction — run the plan/messaging through the customer or prospect panel. Who's delighted, who churns, who shrugs.
Cross-fire — finance vs. growth, sales vs. product, brand vs. speed. Force the real trade-offs into the open.
Risk register — every surfaced risk scored by likelihood × blast radius, with an owner and a mitigation.