DR
Disaster Recovery Plan
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a disaster recovery plan for a service or system — covering RPO/RTO targets, failure scenario runbooks, backup and restore procedures, DR testing cadence, and communication templates. Use when asked to write a DR plan, document failover procedures, create recovery runbooks, define RTO/RPO targets, or prepare for a disaster recovery game day. Produces a full DR document with per-scenario recovery runbooks, backup validation procedures, testing schedule, and communication templates.
What to give it
▸Service name — and what it does (business function and technical role)
▸Criticality tier — business impact of extended downtime (e.g. Tier 1 = revenue-critical, Tier 2 = ops impact, Tier 3 = internal only)
▸Current infrastructure setup — cloud provider, regions/zones, deployment model (Kubernetes, ECS, VMs, serverless)
▸RPO / RTO requirements — Recovery Point Objective (how much data loss is acceptable) and Recovery Time Objective (how long can it be down)
▸Backup strategy — what is backed up, how often, where backups are stored, retention policy
▸On-call contacts — names and contact details for the responder chain
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓RPO and RTO targets are specific numbers, not ranges, and are agreed with the business
✓Every command in every runbook has been run by a human in the last quarter — not copied from documentation untested
✓DR database exists in the DR region and replication lag is monitored
✓Backup restore has been tested end-to-end within the last 7 days
✓The game day schedule is on the team calendar — not just documented here
✓Contact list contains current phone numbers, not just Slack handles (Slack may be down during a DR event)
✓Security breach runbook (3.5) explicitly names the security team contact and does not attempt self-remediation
✓All thresholds (RTO/RPO) are visible in the monitoring dashboard so actual vs. target is measurable in real time
⚠️ What it refuses to do
Do not write runbook commands without testing them — an untested command in a runbook is actively dangerous during a real disaster when cognitive load is highest
Do not set RTO/RPO targets without business sign-off — technical teams often set aspirational targets that do not reflect actual business cost tolerance for downtime
Do not include only the "happy path" of each failover scenario — runbooks must explicitly cover what to do when the recovery step itself fails
Do not list Slack handles as the only escalation contact — Slack may be unavailable during a region-wide failure; phone numbers are mandatory
Do not schedule DR game days without pre-committing to fix the gaps found — a game day that produces action items no one owns is theater, not preparedness
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="disaster-recovery-plan"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Disaster Recovery Plan is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog