pmstudio-drlisted

# DR Plan — Disaster Recovery Plan ## Purpose Generates a Disaster Recovery plan scoped to a specific product. For SaaS products (where the vendor owns infrastructure), this plan focuses on what Coco Inc controls: data exports, integration failover, access recovery, communication, and business continuity. ## Process ### Step 1: Read Context **Read all that exist:** - `CLAUDE.local.md` — architecture, integrations, vendor info, data strategy - `PRD/*.html` or `PRD/*.md` — NFRs, technical considerations, integrations, data architecture - `Architecture/` — system diagrams, data flows - `Operational/IRP-*.html` — incident response plan (if exists, reference for communication) ### Step 2: Determine Product Type From context, classify the product: | Type | DR Focus | Example | |------|----------|---------| | **SaaS (customer)** | Vendor dependency, data portability, alternative workflows | (third-party SaaS) | | **Self-hosted** | Infrastructure recovery, backup/restore, failover | Custom app on EKS | | **Hybrid** | Both vendor and self-hosted components | SaaS + custom middleware | Adjust the plan scope accordingly. For SaaS, skip infrastructure sections (that's the vendor's problem). Add vendor SLA and data portability sections. ### Step 3: Ask Discovery Questions Only ask what can't be inferred: 1. **Business criticality tier?** (Tier 1 critical / Tier 2 important / Tier 3 standard) 2. **What's the maximum tolerable downtime?** (This becomes RTO) 3. **What's the maxi