incident-response

Automate incident response workflows with a five-phase detection-to-postmortem process.

3|4|Updated Mar 20, 2026

Search Tags:#runbook #on-call #postmortem #incident #response #outage

Ready to run

npx skills add https://github.com/jamestorrevillas/dev-skills --skill incident-response-jamestorrevillas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/jamestorrevillas/dev-skills/tree/main/.github/skills/incident-response
Command: npx skills add https://github.com/jamestorrevillas/dev-skills --skill incident-response-jamestorrevillas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable, structured approach to managing production incidents, outages, and critical bugs from detection through post-mortem, reducing mean time to recovery and improving blameless learning.

Core Features & Use Cases

Five-phase playbook: Detect, Assess, Respond, Resolve, and Learn with clear roles and checklists.
Runbook templates: Standardized incident templates for quick starting points and consistent post-mortems.
On-call readiness: Guidance for alerting, escalation, and communications during incidents.

Quick Start

Follow the five-phase workflow to detect, assess, respond, resolve, and learn from an incident.

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I structure incident response workflows for production outages?▼

Incident response workflows are structured using a five-phase playbook that covers detection, assessment, response, resolution, and blameless post-mortem learning. This reduces mean time to recovery by applying clear roles and standardized runbook checklists during on-call investigations.

What is a blameless postmortem and how do I create one for an outage?▼

A blameless postmortem is a structured post-incident review focused on systemic learning rather than individual fault. You create one using standardized runbook templates that guide documentation of the outage timeline, root cause analysis, and preventative action items.

How do I automate on-call escalation decisions during a service outage?▼

On-call escalation decisions during an outage are automated through a structured five-phase incident response process. It evaluates severity during the assessment phase to trigger appropriate alerting, communications, and rollback decisions across critical services.

Can I use a standardized runbook template for all critical service incidents?▼

Yes, you can use standardized runbook templates for all critical service incidents to ensure consistent post-mortems and quick starting points. These templates provide repeatable checklists for detection, response, and restoration across the infrastructure.

What is the best way to reduce mean time to recovery during production incidents?▼

The best way to reduce mean time to recovery during production incidents is following a repeatable five-phase playbook covering detection, assessment, response, resolution, and learning. This structured approach minimizes downtime through rapid rollback decisions and clear on-call roles.