Disaster Recovery Plan

Define recovery objectives (RTO/RPO), backup strategies, failover procedures, and testing protocols. Use when planning disaster recovery or establishing continuity practices.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill disaster-recovery-plan
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/infrastructure-design/skills/disaster-recovery-plan ~/.claude/skills/disaster-recovery-plan

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Disaster Recovery Plan

Design recovery strategies with defined objectives, tested procedures, and regular validation.

## Context

You are planning disaster recovery. Define RTO/RPO requirements, design backup and failover strategies, plan testing. Read business impact analysis, current backups, and regulatory requirements.

## Domain Context

Based on IT disaster recovery best practices (NIST, ISO 27031):

- **RTO (Recovery Time Objective)**: How long can system be down? 1 hour? 1 day? Determines failover strategy.
- **RPO (Recovery Point Objective)**: How much data loss acceptable? 1 hour? 1 day? Determines backup frequency.
- **Backup Strategies**: Full (complete copy), incremental (only changes since last backup), continuous replication
- **Failover**: Automatic (heartbeat-driven) vs manual (operations-triggered). Planned vs unplanned.
- **Testing**: Regular drills validate procedures; practice before disaster strikes

## Instructions

1. **Define Business Requirements**: For each critical system, what's RTO (max downtime) and RPO (max data loss)? Business impact: lost revenue, SLA violations, customer trust?

2. **Design Backup Strategy**: Full daily backup + hourly incremental. Or continuous replication for stricter RPO. Test recovery from backups monthly; document recovery steps.

3. **Plan Failover**: For RTO < 1 hour, set up active-passive (standby system). For RTO < 5 minutes, active-active (both systems live). Implement health checks and automatic failover.
Read the full skill on GitHub

Details

Skill name
disaster-recovery-plan
Path
architect/infrastructure-design/skills/disaster-recovery-plan/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Disaster Recovery Plan skill do?

Define recovery objectives (RTO/RPO), backup strategies, failover procedures, and testing protocols. Use when planning disaster recovery or establishing continuity practices.

How do I install the Disaster Recovery Plan skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Disaster Recovery Plan popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.