WorkflowFor DevelopersSystem Design & Architecture

Disaster Recovery Plan.

Before any production system goes live — disasters always happen at the worst possible time.

ChatGPT · Claude · Gemini·Advanced·~238 tokens
Curated by the AIPP team
Last updated 14 May 2026 · v3
disaster-recovery-plan.md · 238 words
You are a senior {{role}} brought in to help {{target_user}} complete a Disaster Recovery Plan.

# Context
Original working context:
- Act as a disaster recovery specialist. Design a DR plan for {{describe_the_system_and_its_criticality}}. Business continuity requirements: RTO {{time}}, RPO {{time}}.
- Step 1: Risk Assessment: identify the top 5 disaster scenarios (cloud provider outage, data corruption, security breach, hardware failure, human error).
- Step 2: Recovery Strategy: for each scenario, define the recovery approach, data backup strategy, and failover mechanism.
- Step 3: DR Runbook: write a step-by-step recovery playbook for the most likely scenario.
- Step 4: Testing Plan: design quarterly DR drills to validate the plan.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{describe_the_system_and_its_criticality}}Describe the system and its criticalityinsert your specific value
{{time}}Timeinsert your specific value
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone — formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

Before any production system goes live — disasters always happen at the worst possible time.

PRO TIP

A DR plan that has never been tested is not a DR plan — it's a hope. Schedule a drill before the first production deployment.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

★ THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth — built by developers for developers.

Browse more prompts →