incident-runbook-templates

Create structured incident response runbooks with triage steps, escalation matrices, and communication templates.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill incident-runbook-templates-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-runbook-templates
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/incident-runbook-templates
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill incident-runbook-templates-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During a production outage, on-call engineers waste critical minutes improvising procedures, hunting for commands, and forgetting to communicate with stakeholders. This Skill provides ready-to-use runbook templates that turn chaotic incident response into a repeatable, checklist-driven process. ## Core Features & Use Cases - Service Outage Runbooks: Templates covering detection alerts, initial triage, mitigation procedures (kubectl rollbacks, scaling, circuit breakers), verification steps, and rollback paths. - Database Incident Runbooks: Quick-reference SQL and commands for connection pool exhaustion, replication lag, and disk space emergencies, with dry-run safeguards for destructive operations. - Escalation & Communication: Severity classification (SEV1-SEV4), escalation matrices, and pre-written Slack notification templates for initial alerts, status updates, and resolutions. - Use Case: A payments team needs a runbook for their service before launching. Use this Skill to generate a complete runbook with health check commands, rollback procedures, an escalation matrix, and stakeholder communication templates written for a stressed 3 AM responder. ## Quick Start Create an incident response runbook for my payment processing service including triage steps, rollback procedures, and an escalation matrix.

Frequently Asked Questions about incident-runbook-templates

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

FAQPage Schema
How do I write an incident response runbook for a production service?

Structure the runbook with sections for impact assessment, detection alerts, initial triage, mitigation steps, verification, rollback, and escalation. Write commands for a stressed 3 AM responder with prerequisite checks and expected outputs for each step.

How to handle database connection pool exhaustion during an incident?

Query pg_stat_activity to identify connection counts by state and user, then terminate idle connections older than a threshold. Always run a dry-run count query first to verify how many connections will be terminated before executing pg_terminate_backend.

What severity levels should an incident runbook define?

Define four levels: SEV1 for complete outage or data loss with 15-minute response, SEV2 for major degradation at 30 minutes, SEV3 for minor impact at 2 hours, and SEV4 for minimal impact handled next business day.

Why do runbook steps fail during real incidents but work in staging?

Runbook commands often assume preconditions that hold in healthy environments but break during outages. Add prerequisite checks, expected output descriptions, and fallback instructions for every command, such as kubeconfig setup before kubectl calls.

How do I keep incident runbooks from becoming outdated?

Add a Last Verified date and owner at the top of each runbook, review after every SEV1 or SEV2 incident, and validate endpoints and cluster names in CI. Test runbooks regularly through game days or chaos engineering exercises.