disaster-recovery-plan

Define and validate disaster recovery strategies with RTO and RPO targets.

1|Updated Jun 20, 2026

Search Tags:#compliance #resilience #backup #disaster-recovery #chaos-engineering #rpo #rto

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill disaster-recovery-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: disaster-recovery-plan
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/disaster-recovery-plan
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill disaster-recovery-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill transforms vague backup promises into a rigorous, drill-verified disaster recovery capability, ensuring your platform can survive data loss, cluster failure, or regional outages without silent architectural drift.

Core Features & Use Cases

DR Scope Definition: Categorizes failure classes (data, cluster, region, tenant-stamp) with specific RTO and RPO targets.
Continuous Verification: Implements a dual-layer strategy of quarterly full-scale drills and weekly chaos experiments to close the gap between theory and reality.
Use Case: Use this skill to define the recovery strategy for a new microservice, ensuring that PostgreSQL PITR, outbox-based event re-materialization, and crypto-shredding compliance are all accounted for before the first production deployment.

Quick Start

Use the disaster-recovery-plan skill to generate a new DR plan artifact for the current product by following the provided template and referencing the drill guide.

Frequently Asked Questions about disaster-recovery-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define disaster recovery strategies for measured RTO and RPO targets?▼

You can verify disaster recovery plans by implementing a dual-layer strategy of quarterly full-scale drills and weekly chaos experiments. This continuous fault injection closes the gap between theoretical recovery models and actual platform resilience during cluster failures or regional outages.

What is the best way to structure a disaster recovery plan for a new microservice?▼

The best way to structure a disaster recovery plan for a new microservice is to generate a DR plan artifact using a standardized template. This ensures all PostgreSQL PITR, outbox-based event re-materialization, and crypto-shredding compliance requirements are fully accounted for before production deployment.

Does this disaster recovery approach support per-tenant isolation and crypto-shredding?▼

Yes, this disaster recovery approach explicitly satisfies requirements for per-tenant isolation and crypto-shredding consistency. It applies to platform engineering and SRE workflows requiring rigorous backup inventory and automated projection rebuilding across multiple failure classes.

How do I run chaos engineering experiments for continuous disaster recovery verification?▼

Continuous disaster recovery verification uses weekly chaos engineering experiments combined with quarterly full-scale drills. This dual-layer testing strategy ensures your platform can survive data loss, cluster failure, or regional outages without silent architectural drift over time.

When do I need to account for outbox-based event re-materialization in my disaster recovery plan?▼

Outbox-based event re-materialization must be accounted for in a disaster recovery plan when defining the recovery strategy for a new microservice. This ensures PostgreSQL PITR and crypto-shredding compliance are fully validated before the first production deployment.