pmstudio-dr

Generate a SaaS Disaster Recovery plan with numeric RTO and RPO targets.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill pmstudio-dr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmstudio-dr
Source: https://github.com/rkz91/coco/tree/main/skills/dr-plan
Command: npx skills add https://github.com/rkz91/coco --skill pmstudio-dr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Disaster recovery planning for SaaS products where Coco Inc is the customer, focusing on defining and coordinating RTO and RPO targets to protect data, services, and customer trust.

Core Features & Use Cases

  • SaaS-focused DR scope and governance: manage vendor dependencies, data export requirements, and cross-team accountability.
  • RTO/RPO target planning and validation: produce numeric targets per component and ensure alignment with vendor SLAs.
  • Recovery procedures, communication, and testing: outline steps per scenario and a testing cadence.

Quick Start

Create a ready-to-use DR plan document for a SaaS product with numeric RTO and RPO targets.

Frequently Asked Questions about pmstudio-dr

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

FAQPage Schema
What is disaster recovery planning for SaaS products and when do I need it?

Disaster recovery planning for SaaS products defines how to restore data and services after an outage. You need it to set RTO and RPO targets, manage vendor dependencies, and protect customer trust when relying on external SaaS platforms.

How do I create a SaaS disaster recovery plan with numeric RTO and RPO targets?

To create a SaaS disaster recovery plan, define explicit numeric RTO and RPO targets per component, map vendor dependencies and data export requirements, outline failover workflows, and establish communication strategies and testing cadence across incident scenarios.

Can I use this disaster recovery plan for SaaS products where my company is the customer?

Yes, this disaster recovery plan is designed specifically for SaaS products where your company is the customer. It coordinates vendor dependencies, validates SLA alignment, and structures cross-team accountability for your SaaS-focused DR scope.

What is the best way to define RTO and RPO targets across vendor dependencies in a SaaS DR plan?

The best way to define RTO and RPO targets is to produce numeric targets per component and ensure alignment with vendor SLAs. This SaaS DR approach validates that vendor dependencies and data export requirements meet your recovery objectives.

What should a SaaS disaster recovery plan cover for incident scenarios and failover workflows?

A SaaS disaster recovery plan should cover recovery procedures per incident scenario, structured failover workflows, data export requirements, and communication strategies. It must also include a testing cadence to validate that RTO and RPO targets remain achievable.

Why do I need explicit numeric RTO and RPO targets in a SaaS disaster recovery plan?

Explicit numeric RTO and RPO targets are required in a SaaS disaster recovery plan to validate recovery feasibility against vendor SLAs. Without numeric targets, you cannot ensure vendor dependencies, data exports, and failover workflows will protect data and customer trust.