incident-response

Manage incident workflows from detection through mitigation and blameless postmortem documentation.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill incident-response-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/incident-response
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill incident-response-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage real production incidents by turning raw alerts and status updates into a structured response, clear communication, and a blameless postmortem with actionable next steps.

Core Features & Use Cases

  • Incident triage and severity classification: Assess SEV1–SEV4, identify affected systems/users, and assign incident roles (IC, comms, responders) to reduce chaos.
  • Structured communication workflow: Draft internal status updates and customer-facing messaging guidance, then establish war room cadence.
  • Postmortem generation framework: Produce a blameless postmortem template with timeline reconstruction, 5 Whys root cause analysis, and owned action items.

Quick Start

Start by running /incident-response new with a short incident description, then choose “update” for ongoing status and “postmortem” after resolution.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I run a blameless postmortem after a production incident?

A blameless postmortem focuses on systemic issues rather than individual fault. You reconstruct the incident timeline, apply 5 Whys root cause analysis, and assign specific action items with owners to prevent recurrence.

What is the best way to structure mid-incident status updates?

Mid-incident status updates require a structured communication workflow drafting both internal alerts and customer-facing messaging. Establish a war room cadence to regularly distribute updates until the incident is fully mitigated and resolved.

How do I assign roles during incident management to reduce chaos?

Assigning incident roles like Incident Commander, communications lead, and responders reduces chaos during incident management. This role separation ensures clear decision-making authority and structured communication while responders focus on mitigation.

Can I use this for minor degraded service alerts or is it only for major outages?

This incident response workflow applies to both major production outages and degraded service alerts. The severity assessment framework scales from SEV1 critical failures down to SEV4 minor issues, structuring triage and communication accordingly.

When do I need to perform a 5 Whys root cause analysis?

You need to perform a 5 Whys root cause analysis during the post-resolution phase of incident management. It drills down into underlying systemic factors by repeatedly asking why an event occurred, directly informing your action items.