incident-response

Guide production teams through incident response from severity classification to blameless postmortems.

150|48|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/irahardianto/awesome-agv --skill incident-response-irahardianto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/irahardianto/awesome-agv/tree/main/.agents/skills/incident-response
Command: npx skills add https://github.com/irahardianto/awesome-agv --skill incident-response-irahardianto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams structure how to respond to production incidents so that resolution is faster, communication is clearer, and improvements are documented through blameless postmortems.

Core Features & Use Cases

  • Severity classification (P0–P3) to align urgency, response time, and expectations during high-pressure events.
  • End-to-end incident workflow covering detect & alert, triage, diagnosis, mitigation, and resolve, including evidence-based root-cause documentation.
  • Blameless postmortems with action items plus a pre-mortem template to identify likely failure modes before risky work ships.

Quick Start

Use the incident-response skill to guide your team through a new production incident from severity classification through a blameless postmortem and prevention plan.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I structure production incident response for P0 to P3 outages?

Production incident response for P0 to P3 outages is structured through severity classification, triage, diagnosis, and mitigation phases. This workflow aligns urgency expectations and ensures faster resolution with evidence-based root cause documentation.

What is a blameless postmortem and how does it prevent future incidents?

A blameless postmortem is an evidence-based incident review process that focuses on systemic root causes rather than individual errors. It generates SMART action items to drive operational resilience and reduce the recurrence of similar production outages.

How do I classify incident severity during a production outage?

Incident severity classification categorizes production events from P0 to P3 to align urgency, response time, and expectations. This classification dictates the required response intensity for outages and service degradation across operational workflows.

When should I run a pre-mortem risk assessment for operational resilience?

A pre-mortem risk assessment should be run before risky work ships to identify likely failure modes. It helps operational teams anticipate potential service degradation scenarios and proactively design mitigation strategies for production systems.

Can I use this incident response workflow for service degradation and not just full outages?

Yes, this incident response workflow applies to both full outages and service degradation events. It guides teams through the same severity classification, triage, diagnosis, and mitigation process regardless of the operational impact level.

What do I need to document during root cause analysis for an on-call incident?

Root cause analysis during an on-call incident requires evidence-based documentation of the diagnosis and mitigation phases. This documentation forms the foundation for the blameless postmortem and generates SMART action items to prevent recurrence.