pmstudio-irp

Generate a product-specific Incident Response Plan as a self-contained HTML document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates a product-specific Incident Response Plan (IRP) by reading the product context (PRD, stakeholder directory, and project memory) to produce a tailored, ready-to-use plan for incident handling.

Core Features & Use Cases

  • Tailored IRP generation: uses real stakeholders and product context to construct escalation, containment, and communication procedures.
  • Offline, self-contained document: outputs a 12-section HTML plan suitable for offline use during incidents.
  • Use cases: product security incidents, outages, data incidents, and regulatory inquiries requiring a documented response.

Quick Start

Provide a product context (PRD, stakeholder directory, and project memory) and request an IRP tailored to that product.

Frequently Asked Questions about pmstudio-irp

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

FAQPage Schema
How do I generate an incident response plan tailored to a specific product?

Generate a tailored incident response plan by providing product context like the PRD, stakeholder directory, and project memory to automatically construct severity classification, escalation paths, and response procedures.

What should be included in a product incident response playbook for outages and security incidents?

A product incident response playbook should include severity classification, detection and reporting, escalation matrix, communication protocol, evidence preservation, and post-incident review sections tailored to actual stakeholders.

Can I create an offline incident response plan that works without external dependencies?

You can create a self-contained offline incident response plan that outputs a standalone HTML document with 12 sections, requiring no external dependencies for use during active incidents.

How do I map stakeholder communications and escalation paths for a product incident?

Map stakeholder communications and escalation paths by reading the stakeholder directory and project memory to generate tailored communication protocols and an escalation matrix for specific product scenarios.

Does generating an incident response plan require specific input formats?

Generating an incident response plan requires providing product context inputs, specifically the product requirements document, stakeholder directory, and project memory, to tailor the output procedures accurately.

What is the best way to document resolution and recovery procedures for data incidents?

Document resolution and recovery procedures for data incidents by generating a structured response plan that outlines evidence preservation, containment steps, and post-incident review based on your specific product context.