Agent skill · product strategy · onewave-ai
product-launch-war-room
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.
Why this skill is useful
Provides a structured approach to managing product launches with risk assessment and stakeholder engagement that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-07-15. 242 stars on the source repository.
What this skill does
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 1. Pre-mortem — "It's 90 days post-launch and it flopped. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills onewave-ai/product-launch-war-room