triage-incident

Classify production incident severity and coordinate mitigation and handoff.

Updated Dec 21, 2018
One-click install
npx skills add https://github.com/dhnt/dhnt --skill triage-incident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-incident
Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/operate/triage-incident
Command: npx skills add https://github.com/dhnt/dhnt --skill triage-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you triage a live production incident by assessing severity, containing blast radius, and coordinating a clean handoff without prematurely chasing root cause.

Core Features & Use Cases

  • Incident severity classification to quickly decide who to page and how aggressively to stop other work.
  • Blast-radius assessment and mitigation-first actions to restore service using the smallest effective intervention (rollback, scaling, feature flags, rate limiting, routing changes).
  • Operational communication and handoff discipline with a consistent incident timeline, regular updates, and a scheduled post-mortem.

Use case: A new deploy causes elevated errors and latency; you need to decide Sev1 vs Sev2, mitigate immediately (rollback/traffic drain/flag), keep stakeholders updated, and transfer context for resolution.

Quick Start

Ask your AI assistant to run triage-incident for the current on-call alert, producing a timeline, current state, known facts, unclear items, and next mitigation actions.

Frequently Asked Questions about triage-incident

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

FAQPage Schema
How do I triage a live production incident and decide its severity classification?

To triage a production incident, classify its severity to determine paging urgency, contain the blast radius using the smallest effective intervention, and coordinate mitigation until resolution or handoff.

What is the best way to mitigate a service outage without chasing root cause?

The best way to mitigate a service outage is applying a mitigation-first approach: rollback, scale, toggle feature flags, or adjust routing to restore service quickly before investigating root cause.

How does blast radius containment work during an on-call alert?

Blast radius containment works by executing the smallest effective intervention—like rolling back, draining traffic, or rate limiting—to stabilize the incident and prevent further customer impact.

How do I structure operational communication and handoff for an active incident?

Structure operational communication by maintaining an incident timeline, providing regular status updates, and creating clean handoff artifacts to transfer context for resolution.

When do I need to schedule a post-mortem after resolving an operational failure?

You need to schedule a post-mortem immediately after an operational failure is resolved to document the incident timeline, analyze mitigation actions, and prevent recurrence.

Can I use incident triage for feature breakage and service degradation, or only full outages?

You can use incident triage for customer outages, service degradation, feature breakage, and other real-time operational failures, adapting severity classification and mitigation actions accordingly.