pmstudio-dr

Generate disaster recovery plans for SaaS products with RTO and RPO targets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create a practical disaster recovery plan for a SaaS product when business continuity, data recovery, access recovery, and vendor dependency risks need to be documented clearly.

Core Features & Use Cases

  • RTO/RPO Planning: Defines recovery time and recovery point targets for core services, integrations, and data flows.
  • Scenario-Based Recovery: Organizes response steps for outages, corruption, access loss, security incidents, and vendor failure.
  • Business Continuity Support: Captures manual workarounds, communication paths, backup expectations, testing cadence, and review responsibilities.
  • Use Case: A product team can use this Skill to produce a complete DR plan for a customer-facing SaaS platform with clear recovery targets and stakeholder actions.

Quick Start

Create a disaster recovery plan for the named SaaS product and include RTO and RPO targets, recovery scenarios, manual workarounds, communication steps, backup strategy, and testing schedule.

Frequently Asked Questions about pmstudio-dr

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

FAQPage Schema
How do I create a disaster recovery plan for a SaaS product?

A SaaS disaster recovery plan requires defining explicit RTO and RPO targets, mapping recovery steps for outages and data corruption, establishing manual workarounds, and scheduling testing controls. It structures response actions across multiple failure scenarios to ensure business continuity.

What should be included in SaaS business continuity planning for vendor failure?

SaaS business continuity planning for vendor failure requires documented manual workarounds, defined communication paths, backup expectations, and restoration steps. It must also capture explicit recovery time and recovery point targets specific to the identified vendor dependency risks.

How do RTO and RPO targets factor into disaster recovery planning?

RTO and RPO targets define the maximum acceptable downtime and data loss for core services during an incident. These targets drive the required backup strategies, restoration steps, and manual workarounds necessary to meet specific business continuity recovery objectives.

Can I use this approach to plan for SaaS security incidents and access loss?

Yes, this disaster recovery planning approach explicitly supports SaaS security incidents and access loss. It organizes scenario-based response steps for outages, data corruption, access loss, integration failures, and security incidents alongside defined recovery targets and communication planning.

Does a disaster recovery plan require manual workarounds and testing schedules?

A disaster recovery plan requires manual workarounds and testing schedules to ensure operational resilience during outages. Documenting these workarounds alongside communication paths and review responsibilities ensures the SaaS product maintains business continuity while underlying recovery steps execute.