home / skills / gtmagents / gtm-agents / war-room-ops

This skill orchestrates launch standups and escalation workflows, enabling rapid cross-functional decisions and clear, documented stakeholder communication

npx playbooks add skill gtmagents/gtm-agents --skill war-room-ops

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: war-room-ops
description: Use when running launch command centers, standups, and escalation workflows.
---

# War-Room Operations Skill

## When to Use
- Launches requiring daily standups and cross-functional coordination.
- Managing high-risk windows (launch week, pricing changes, major PR events).
- Ensuring swift resolution of issues and clear stakeholder comms.

## Framework
1. **Cadence & Channels** – schedule standups, async updates, and escalation channels (Slack, pager, email).
2. **Rituals** – agenda for standups (status, blockers, metrics), risk reviews, exec syncs.
3. **Escalation Paths** – define severity levels, decision owners, fallback contacts.
4. **Documentation** – central log for decisions, incidents, mitigations, deployments.
5. **Monitoring Hooks** – dashboards, alert routing, on-call rotations, support coverage.

## Templates
- War-room charter (objectives, team, schedule, SLAs).
- Standup template (status, blockers, next actions, owners).
- Escalation matrix (severity, trigger, contact tree, resolution target).

## Tips
- Keep war-room staffed with empowered decision makers.
- Record all decisions + rationale for post-launch retros.
- Automate reminders for updates to reduce noise.

---

Overview

This skill provides a production-ready war-room operations playbook for running launch command centers, daily standups, and escalation workflows. It bundles cadence templates, escalation matrices, and documentation patterns to keep cross-functional teams aligned during high-risk windows. The goal is to speed decision-making, reduce noise, and ensure clear stakeholder communication.

How this skill works

The skill defines a repeatable framework: schedule cadences and channels, set standup rituals, and map escalation paths with owners and fallback contacts. It supplies templates for charters, standups, and escalation matrices, and recommends monitoring hooks and a central decision log. Automation tips include reminders and alert routing to minimize manual overhead.

When to use it

  • Running a product launch, pricing change, or other time-sensitive release requiring tight coordination
  • Managing a high-risk event window (launch week, major PR, or regulatory change)
  • Coordinating cross-functional daily standups and status syncs
  • When rapid incident resolution and clear stakeholder comms are required
  • During on-call rotations that must integrate with GTM and support teams

Best practices

  • Staff the war-room with empowered decision makers only—avoid crowding with observers
  • Use a concise standup agenda: status, blockers, metrics, next actions, and owners
  • Define clear severity levels and escalation paths, including decision owners and fallbacks
  • Maintain a central log of decisions, rationale, mitigations, and deployment timestamps
  • Automate reminders and alert routing to reduce manual pings and meeting overload

Example use cases

  • Launch week command center coordinating product, marketing, sales, and support
  • Emergency response for a major outage affecting revenue-critical flows
  • Coordinating pricing rollout across regions with legal and finance signoff
  • Standup-driven risk review during a phased feature release
  • Post-launch retrospective driven by recorded decisions and incident logs

FAQ

Who should be in the war-room?

Include empowered decision owners from product, engineering, customer success, sales, and comms. Keep the core team small and invite specialists as needed.

How do I avoid noisy updates?

Standardize update formats, automate reminder cadence, and route only actionable alerts to the war-room channel. Use async updates for low-priority items.