---
name: disaster-recovery-plan-creator
description: "Drafts a business disaster recovery plan with recovery targets, priority functions, backup strategy, activation steps, and a test schedule. Use when a business owner or IT lead must write or refresh a disaster recovery plan with recovery time and recovery point targets. Do not use for incident response to a live attack or a general business continuity policy. Related topics: disaster, recovery, plan."
---

# Disaster Recovery Plan Creator

Drafts a business disaster recovery plan with recovery targets, priority functions, backup strategy, activation steps, and a test schedule.

## When to use

Use this skill when a business owner or IT lead must write or refresh a disaster recovery plan with recovery time and recovery point targets. Do not use it for incident response to a live attack or a general business continuity policy.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Rank the critical functions by required recovery speed and attach the recovery time objective to each.
3. Test the backup frequency against the recovery point objective and flag any gap with a fix.
4. Write a first-hour runbook for each selected disaster naming who does what.
5. Define the activation decision, the contact tree, and staff and customer messaging.
6. Create a test script with explicit pass criteria and a schedule that matches the chosen frequency.

## Inputs

- **Company name** (free text, e.g. "Name")
- **Industry** (choose one: Finance, Healthcare, Technology, Manufacturing, Other)
- **Location** (free text, e.g. "City and country")
- **Recovery time objective in hours** (number from 1 to 72)
- **Recovery point objective in hours** (number from 0 to 24)
- **Critical business functions** (longer free text)
- **Disasters to prepare for** (choose any: Natural Disasters, Cyber Attacks, Power Outages, Supply Chain Disruptions, Other)
- **Likely impact on operations** (longer free text)
- **Emergency contact** (free text, e.g. "Name and phone")
- **Backup approach** (choose one: Cloud, On-Premise)
- **Backup frequency** (choose one: Daily, Weekly, Monthly)
- **Offsite storage location** (free text, e.g. "Where")
- **Activation** (choose one: Automatic, Manual)
- **Testing frequency** (choose one: Quarterly, Bi-Annually, Annually)
- **Testing team** (longer free text)

## Output

A plan with sections for objectives, function ranking, per-disaster runbooks, communications, activation, and testing. A gap list sits at the top if any target is unmet.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Disaster Recovery Plan

Draft a disaster recovery plan for my business.

- Company name: {{Company name}}
- Industry: {{Industry}}
- Location: {{Location}}
- Recovery time objective in hours: {{Recovery time objective in hours}}
- Recovery point objective in hours: {{Recovery point objective in hours}}
- Critical business functions: {{Critical business functions}}
- Disasters to prepare for: {{Disasters to prepare for}}
- Likely impact on operations: {{Likely impact on operations}}
- Emergency contact: {{Emergency contact}}
- Backup approach: {{Backup approach}}
- Backup frequency: {{Backup frequency}}
- Offsite storage location: {{Offsite storage location}}
- Activation: {{Activation}}
- Testing frequency: {{Testing frequency}}
- Testing team: {{Testing team}}

Rank the critical functions by how fast they must return, then check that the backup frequency can actually meet the recovery point objective. If it cannot, say so and recommend a change. For each selected disaster, give a short response runbook with who does what in the first hour. Include communication steps for staff and customers, the activation decision, and a test script with pass criteria. Note any compliance rules common to the industry.

## Pitfalls

- Setting a recovery point objective that the backup frequency cannot meet.
- Writing runbooks by role title without a named person and backup person.
- Never testing a restore, so the plan fails when it is needed.
