risk-playbooks

Build launch risk registers with scored risks, named owners, triggers, and rollback plans.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill risk-playbooks-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-playbooks
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/risk-playbooks
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill risk-playbooks-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Launch planning often misses honest risk assessment: teams skip pre-mortems, assign risks to functions instead of people, define vague rollback triggers, and forget to brief support. This Skill structures launch risk identification, scoring, mitigation, and escalation so red-cell risks get real playbooks before launch week. ## Core Features & Use Cases - Pre-mortem facilitation: Forces the team to imagine the failure state and surface risks that forward-looking planning misses. - Risk register with scoring: Scores each risk on likelihood and impact (1-3 each), with red/yellow/green bands determining whether a full playbook, one-line mitigation, or acknowledgement is required. - Triggers, owners, and rollback discipline: Requires named primary and backup owners, observable metric-based triggers, rehearsed sub-15-minute rollbacks, and severity levels (Sev-1 to Sev-4) tied to pre-agreed responses. - Use Case: Before launching a new checkout flow, use this Skill to run a pre-mortem, build a risk register with scored entries, assign named owners with backups, define alert-wired triggers, and rehearse the feature-flag rollback. ## Quick Start Help me run a pre-mortem and build a risk register for our product launch next month, including owners, triggers, and rollback plans for the top risks.

Frequently Asked Questions about risk-playbooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-mortem before a product launch?

Ask the team to imagine it is two weeks after launch and the launch failed, then have each person write down what caused the failure. This inverts the bias toward denial and surfaces risks that forward-looking planning misses.

How do I prioritize launch risks in a risk register?

Score each risk 1-3 on likelihood and 1-3 on impact, then multiply. Scores of 7-9 get a full playbook with trigger, mitigation, rollback, and rehearsal; 4-6 get a named owner and one-line mitigation; 1-3 are acknowledged only.

What makes a good rollback trigger for a launch?

A good trigger is a specific metric, threshold, observation window, and alert source agreed before launch, such as error rate above 2% sustained over 5 minutes on the checkout path. Vague triggers like 'things seem bad' turn escalation into debate.

Why should risks have named owners instead of team owners?

Functional ownership like 'Engineering owns this' evaporates under pressure. Each red-cell risk needs a named primary and backup person with direct contact info so accountability persists during an incident.

When should support be involved in launch planning?

Support should be briefed, staffed, and given an engineering escalation path before launch, not after. Users report experience failures before dashboards detect them, so support is the first detector of production problems.