Recovery Plan — Service Restoration Runbooks

Recovery Plan — Service Restoration Runbooks

Purpose

Generates step-by-step runbooks for each disaster scenario defined in the DR plan. These are tactical execution documents — meant to be followed during an actual incident by someone who may not be the person who wrote the plan.

Prerequisites

Hard dependency: A DR plan must exist at Operational/DR-Plan-*.html. If not found, respond:

"No DR plan found for this project. The recovery plan is built from DR plan scenarios and RTO/RPO targets. Run /dr-plan first to create one, then run /recovery-plan to generate the runbooks."

Process

Step 1: Read Context

Required:

• Operational/DR-Plan-*.html — scenarios, RTO/RPO targets, dependencies, communication plan
• CLAUDE.local.md — architecture, contacts, integrations

Optional (enriches the runbooks):

• Operational/IRP-*.html — escalation matrix, communication templates
• PRD/*.html — integrations detail, technical considerations
• Architecture/ — system diagrams for reference

Step 2: Extract Scenarios

From the DR plan, extract:

• Each disaster scenario (name, description, trigger condition)
• RTO/RPO targets per component
• Dependencies and contacts
• Manual workarounds

Step 3: Generate Runbooks

Output: Operational/Recovery-Procedures-{ProductName}-{Date}.html

Self-contained HTML. Zero CDN dependencies — this must work offline during recovery.

Structure: One runbook per disaster scenario, plus a general section.