pmstudio-recovery

Generate executable HTML recovery runbooks from disaster plans and scenarios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically translate disaster recovery plans into concrete, executable runbooks that guide on-call engineers through rapid service restoration.

Core Features & Use Cases

  • Generates step-by-step, scenario-specific runbooks from DR plans for on-call incident response.
  • Produces self-contained HTML documents suitable for offline use, with pre-conditions, recovery steps, verifications, and escalation points.
  • Use Case: When an outage triggers a disaster scenario, quickly produce a structured runbook to guide restoration efforts.

Quick Start

Run the recovery plan command after ensuring a DR plan exists at Operational/DR-Plan-*.html to generate offline recovery runbooks.

Frequently Asked Questions about pmstudio-recovery

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

FAQPage Schema
How do I generate executable recovery runbooks from a disaster recovery plan?

To generate recovery runbooks, you need a DR plan located at Operational/DR-Plan-*.html. The tool processes this input along with architecture notes to produce step-by-step restoration procedures for on-call incident response teams.

What is a disaster recovery runbook and how does it help during an outage?

A disaster recovery runbook is a structured, scenario-specific document guiding on-call engineers through rapid service restoration. It includes pre-conditions, recovery steps, verifications, and escalation points to ensure structured incident response.

Can I use generated runbooks offline during an incident response?

Yes, the generated runbooks are self-contained HTML documents with zero CDN dependencies. This ensures they remain fully accessible and executable offline during an outage or disaster scenario.

Do I need an existing DR plan file to create actionable runbooks?

Yes, an existing DR plan at the path Operational/DR-Plan-*.html and related architecture notes are required. These inputs provide the operational context needed to generate specific restoration procedures.

What's the best way to translate DR plans into step-by-step restoration procedures?

The best way is to automate the translation by processing your DR plan into scenario-specific runbooks. This approach creates structured, executable procedures with pre-conditions, verifications, and escalation points.

Are there limitations when generating offline HTML recovery runbooks for multiple components?

The tool requires a properly formatted DR plan at Operational/DR-Plan-*.html and related architecture notes to map restoration across multiple components. Without these inputs, it cannot generate the structured runbooks.