Skip to main content
skill CX Codex

risk-playbooks — Claude Code skill for launch risks

risk-playbooks is a Claude Code skill that assesses launch risks, assigns owners, and plans responses. Use it before a release, during launch, or in a post-launch review.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add gtmagents/gtm-agents --skill risk-playbooks -a claude-code
Open on GitHub

What risk-playbooks does

The skill outlines a repeatable risk review: score each risk by likelihood and impact, then assign an owner, mitigation, trigger, and fallback action. Its categories cover product readiness, go-to-market work, compliance, support, and external factors. That structure keeps the review broader than a bug list.

Included templates cover a risk register, an escalation plan, and lessons learned. Teams can maintain the risk log during war-room standups, record resolutions, and carry findings into future launch guidance. For Tier 1 launches, the skill recommends sharing a daily summary with executives.

What it helps with

  • score launch risks by likelihood and impact
  • assign owners and mitigation steps
  • map escalation triggers to fallback actions
  • carry post-launch lessons into future plans

Example prompts for the agent

  • Assess the risks for this launch and assign likelihood, impact, and an owner to each.
  • Draft an escalation plan with triggers, communications, and response paths.
  • Review this launch and capture lessons for future playbooks.

How to install risk-playbooks

1Skills CLI (Vercel)

npx skills add gtmagents/gtm-agents --skill risk-playbooks -a claude-code

2Manually: put the files in place

~/.claude/skills/risk-playbooks/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/risk-playbooks/

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

Questions about risk-playbooks

How do I install risk-playbooks in Claude Code?

Run npx skills add gtmagents/gtm-agents --skill risk-playbooks -a claude-code. The skill file is at ~/.claude/skills/risk-playbooks/SKILL.md.

What does risk-playbooks do?

It guides launch risk assessment, ownership, and mitigation planning. It includes templates for a risk register, escalation plan, and lessons learned.

Which risk areas does the skill cover?

It covers product readiness, go-to-market work, compliance, support, and external factors such as competitor moves or press sentiment.

Source text

SKILL.md · Apache-2.0
---
name: risk-playbooks
description: Use when identifying launch risks, mitigation plans, and escalation owners.
---

# Launch Risk Playbooks Skill

## When to Use
- Pre-launch risk assessments and go/no-go criteria.
- During launch week to monitor escalations and coordinate mitigations.
- Post-launch retros to capture lessons and update future playbooks.

## Framework
Launch risk governance combines categorical coverage with a repeatable execution cadence. Use the following building blocks to keep Tier 1+ launches on track.

### Risk Categories
1. **Product & Reliability** – feature readiness, bugs, infrastructure load, rollback paths.
2. **Go-to-Market** – messaging accuracy, asset approvals, channel readiness, partner alignment.
3. **Compliance & Legal** – policy reviews, privacy terms, licensing, regional constraints.
4. **Support & Success** – staffing levels, escalation handoffs, enablement coverage.
5. **External Factors** – competitor moves, macro events, press sentiment, supply chain.

### Execution Process
1. Identify risks w/ likelihood + impact scoring.
2. Assign owners, mitigation steps, triggers, fallback actions.
3. Maintain real-time risk log during war-room standups.
4. Capture resolution notes + update future tiering guidelines.

## Templates
- Risk register (description, likelihood, impact, owner, mitigation, status).
- Escalation playbook (trigger, communication plan, action tree).
- Lessons learned tracker feeding future launches.

## Tips
- Pre-populate risk banks per tier to accelerate planning.
- Tie mitigations to instrumentation/alerts to catch issues early.
- Share summaries with execs daily during Tier 1 launches.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar skills

All skills for Marketing and content →

From the same set224

The whole set →
build-technical-bid-plan build-technical-bid-plan generates a technical bid plan covering solution architecture, bill of materials, validation pilots, and pricing models. CX Codex +1 ★ 450repo stars design-partner-ecosystem The design-partner-ecosystem command for Claude Code plans partner tiers, operating rules, and investment priorities for chosen markets and partner types. CX Codex +1 ★ 450repo stars launch-brand-kit launch-brand-kit gathers updated brand guidelines, logos, templates and training plans for marketing, sales and product teams. CX Codex +1 ★ 450repo stars build-playbook build-playbook generates complete sales playbooks with messaging frameworks, asset outlines, and rollout metrics for specific motions. CX Codex +1 ★ 450repo stars review-financial-campaign review-financial-campaign runs compliance review for financial services campaigns against FINRA, SEC and CFPB rules: spots missing disclosures, routes for approval and assembles an audit-ready package. CX Codex +1 ★ 450repo stars run-compliance-review run-compliance-review — a Claude Code command that runs a regulatory compliance review for healthcare marketing campaigns against HIPAA, FDA, and FTC rules. Covers email, landing, paid, webinar, field, and events channels. CX Codex +1 ★ 450repo stars produce-campaign-report The produce-campaign-report command combines campaign channel data with CRM pipeline and revenue fields, then produces findings and recommended actions. Use it to review performance over a chosen window. CX Codex +1 ★ 450repo stars define-brand-platform define-brand-platform turns positioning, messaging pillars, tone and a rollout plan into a deck, a narrative or a workspace document. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open