Skip to main content
skill CX Codex

product-launch-war-room — Claude Code skill: what it does

product-launch-war-room is a Claude Code skill that tests a launch plan against expert and customer viewpoints, then returns a decision and rollout steps. Run it for a product launch, repricing, or repositioning.

MIT 159 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill product-launch-war-room -a claude-code
Open on GitHub

What product-launch-war-room does

The skill convenes a launch review, assigns viewpoints, and asks each role to identify likely failure points. It then produces a go, revise, delay, or no-go call, with ranked risks, owners, and mitigations.

The deliverable includes rollout phases, task owners and deadlines, plus thresholds for pausing or rolling back. Customer perspectives can come from personas in personas/; if that folder is missing and tools are connected, the skill can run icp-deep-scanner in read-only mode. Without either source, it labels the grounding as provisional. Connections stay read-only: the skill sends no messages and uses no real personal data.

What it helps with

  • surface launch risks before release
  • test a price change against customer reactions
  • compare sales, finance, and product objections
  • assign owners and deadlines across rollout phases
  • set pause and rollback thresholds

Example prompts for the agent

  • Review this feature launch for existing customers and rank the main risks.
  • Assess this price increase from customer, sales, and finance perspectives.
  • Turn this launch plan into rollout phases with owners and rollback criteria.

How to install product-launch-war-room

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill product-launch-war-room -a claude-code

2Manually: put the files in place

~/.claude/skills/product-launch-war-room/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/product-launch-war-room/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about product-launch-war-room

How do I install product-launch-war-room in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill product-launch-war-room -a claude-code. The skill file is at ~/.claude/skills/product-launch-war-room/SKILL.md.

What does product-launch-war-room do?

It runs a launch review with expert and customer viewpoints, identifies risks, and returns a decision with rollout phases, owners, and stop criteria.

How does the skill get customer perspectives?

It loads personas from personas/. If the folder is absent but tools are connected, it runs icp-deep-scanner read-only; otherwise, it marks the assessment as provisional.

Source text

SKILL.md · MIT
---
name: product-launch-war-room
description: 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.
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, Agent
model: inherit
---

# 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. What happened?" Each role writes the most likely failure in their lane.
2. **Customer reaction** — run the plan/messaging through the customer or prospect panel. Who's delighted, who churns, who shrugs.
3. **Cross-fire** — finance vs. growth, sales vs. product, brand vs. speed. Force the real trade-offs into the open.
4. **Risk register** — every surfaced risk scored by likelihood × blast radius, with an owner and a mitigation.

## Step 4 — Decide and sequence

```markdown
# Launch War Room — {Launch}
Generated: {timestamp} · Room: {roles/personas} · Reversibility: {…} · Grounding: {data / PROVISIONAL}

## Call: {GO / GO WITH CHANGES / DELAY / NO-GO}
The reasoning in one paragraph.

## Top risks (ranked)
| Risk | Likelihood | Blast radius | Owner | Mitigation | Pre-launch or live? |

## Required changes before launch
- The non-negotiables surfaced by the room.

## Phased rollout
- Phase 0 — prep & internal enablement (sales, support scripts, FAQ)
- Phase 1 — soft launch / segment / beta + what we watch
- Phase 2 — full launch + channels + sequencing
- Phase 3 — post-launch monitoring window

## Kill criteria & rollback
- The specific metric thresholds that trigger pause or rollback, and how to walk it back.

## Owners & timeline
| Workstream | Owner | Deadline | Dependency |

## Comms kit to produce next
- Customer email, sales talk track, support FAQ, objection handling, public page.
```

## Step 5 — Hand off the artifacts
Offer to generate the comms kit (`cold-email-sequence-generator`, `landing-page-copywriter`, `company-announcement-writer`), route a price change to `pricing-change-strategist`, build the launch video with `hyperframes-ad-director`, or re-run the room against the revised plan.

## Guardrails recap
Adversarial by default — the room's job is to find the failure, not bless the plan · rigor scales with reversibility · kill criteria are mandatory, not optional · read-only connections, no sends, no real PII · provisional grounding is labeled.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Marketing and content →

From the same set185

The whole set →
claude-design-system-architect claude-design-system-architect is a Claude Code skill that turns a brand brief or existing site into reusable design tokens, component specs, and project files. It defines shared rules for a new product or inconsistent UI. CX Codex +1 172installs prospect-panel-simulator prospect-panel-simulator is a skill that simulates buyer reactions to sales and marketing materials before they go live, surfacing objections and likely next actions. CX Codex +1 164installs customer-panel-of-experts customer-panel-of-experts assembles a panel of buyer personas to debate product changes, price hikes, or launches before committing resources. CX Codex +1 162installs icp-deep-scanner The icp-deep-scanner skill turns data from connected tools into an Ideal Customer Profile and a persona library. Use it when you need to refresh your ICP or build buyer personas from actual data, not guesses. CX Codex +1 161installs pricing-change-strategist pricing-change-strategist plans a price increase or tier restructure with churn modeling. CX Codex +1 158installs hyperframes-sales-demo-builder hyperframes-sales-demo-builder — a skill for Claude Code, Codex, Cursor and other platforms that builds a prospect-specific demo video in HyperFrames. CX Codex +1 157installs before-you-build The before-you-build skill identifies the main risk in an idea and suggests a small test before implementation starts. Use it to assess a product, feature, MVP, agent, or automation. CX Codex +1 130installs typography-scale-builder typography-scale-builder — a Claude Code skill that designs typographic systems with modular or fluid type scales. It audits existing font values across the codebase and outputs design tokens, CSS, and Tailwind configs. CX Codex +1 116installs

Project sponsors

Companies that keep this analytics open