disaster-recovery-plan
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.
npx skills add mohitagw15856/pm-claude-skills --skill disaster-recovery-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Produces a complete disaster recovery plan for a service or system, including RPO/RTO targets, failure scenario runbooks, backup and restore procedures, DR testing cadence, and communication templates. It is intended to be used 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. It generates a full DR document with per-scenario recovery runbooks, backup validation procedures, testing schedule, and communication templates.
How it works
Follows the structure shown in the Output Format:
- Collects inputs such as service name, criticality tier, current infrastructure, RPO/RTO requirements, backup strategy, and on-call contacts.
- Outlines sections: Recovery Targets, Failure Scenario Inventory, Failure Scenario Runbooks, and Backup/Restore Procedures, each with concrete steps, commands, and references to runbooks (e.g., 3.1 Single Availability Zone Failure, 3.2 Full Region Failure, 3.3 Database Corruption or Data Loss, etc.).
- For each failure scenario, provides trigger, detection, expected RTO/RPO, and a sequence of shell commands and kubectl/aws commands to execute in order, including validation checks and recovery confirmation criteria.
- Includes explicit steps for backup/restore configuration, data restoration, and cutover verification, with commands to manage deployments, databases, DNS, and monitoring.
When to use it
Triggered by the need to create a DR plan, document failover procedures, generate recovery runbooks, define RTO/RPO targets, or prepare for a DR game day. The plan enumerates action steps across multiple failure types and prescribes runbooks to execute during incidents.
What it can touch
References commands and tools explicitly listed in the plan, such as kubectl, AWS CLI commands (aws rds promote-read-replica, aws route53 change-resource-record-sets, etc.), curl, and psql. It describes how to interact with deployment environments, databases, DNS, and monitoring to implement failover and recovery steps.
Caveats
Contains explicit operational steps and command lines but relies on placeholders ([service-name], [namespace], etc.) that must be filled in for a real environment. Targets, runbooks, and backups are described with example values and require real data to implement. Licensing and tool usage align with MIT license, and tools listed include claude-code and cursor.
# Disaster Recovery Plan Skill Produce a complete disaster recovery plan for a service or system — giving engineers, SREs, and on-call responders everything they need to recover from a disaster scenario in the shortest possible time. A good DR plan is tested regularly, has exact commands (not vague instructions), and makes RTO/RPO targets measurable so the team knows whether recovery succeeded. ## Required Inputs Ask for these if not already provided: - **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 ## Output Format --- # Disaster Recovery Plan: [Service Name] **Team:** [Team name] | **Tech l
- Required Inputs
- Output Format
- 1. Recovery Targets
- 2. Failure Scenario Inventory
- 3. Failure Scenario Runbooks
- 3.1 Single Availability Zone Failure
- 3.2 Full Region Failure
- 3.3 Database Corruption or Data Loss
- 3.4 Critical Dependency Outage
- 3.5 Security Breach or Ransomware
- 3.6 Accidental Bulk Data Deletion
- 4. Backup and Restore Procedures
- Backup Configuration
- Backup Validation (Run Weekly)
Check pod/instance health across zones kubectl get pods -o wide -n [namespace] | grep -v Running Check which nodes are affected kubectl get nodes -o wide | grep -v Ready Verify cloud provider AZ status If using auto-scaling, check if replacement instances launched kubectl get pods -n [namespace] --watch Check deployment replica count kubectl get deployment [service-name] -n [namespace] Verify load balancer health checks are passing
What does the disaster-recovery-plan skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill disaster-recovery-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.