domains / families / devops / incident-runbook-templates

incident-runbook-templates

combined

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures. Adaptable templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication.

When to use

• Creating incident response procedures
• Building service-specific runbooks
• Establishing escalation paths
• Documenting recovery procedures
• Responding to active incidents
• Onboarding on-call engineers

When not to use

• The task is unrelated to incident runbook templates
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same severity table, runbook structure, and most of the Service Outage template, but they disagree on safety-critical steps. The sickn33 copy adds a 'Runbook prerequisites' section requiring binding of service/namespace/cluster context, approved incident authority, and evidence sources before adapting templates, and it explicitly states that thresholds and financial amounts are illustrative. It also replaces the direct 'pg_terminate_backend' command with a guarded procedure requiring an exact authorized PID and the approved database runbook. The rmyndharis copy lacks these constraints and includes the direct termination command. Crowning one copy would hide the other's safety constraints and the conflicting mitigation step.