Runs a production incident from declaration to blameless postmortem – SEV1-SEV4 levels with measurable criteria, the four roles (incident commander, comms, ops, scribe) and what each must and must not do, an update cadence per SEV with internal and customer templates.
Runs a production incident from declaration to blameless postmortem - SEV1-SEV4 levels with measurable criteria, the four roles (incident commander, comms, ops, scribe) and what each must and must not do, an update cadence per SEV with internal and customer templates, a timestamped decision log appended to the Release Dossier, a structured IC handoff, and a postmortem section with timeline, contributing factors, 5-whys per factor, and owned, dated action items. Use when someone says "we have an incident", "declare a SEV", "who is IC", "write the status update", "hand off the incident", "start the postmortem", or when a progressive-rollout gate aborts and impact continues. Do NOT use for the revert-or-fix decision itself - use rollback-or-roll-forward instead; for authoring standing service runbooks, use runbook-writer; for a routine on-call shift handoff with no active incident, use oncall-handoff; for a quick severity call on a single alert, use sev-triage; for a standalone postmortem with no Release Dossier, use postmortem-writer.This is the skill's description: the text your AI reads to decide when the skill applies.
incident-command/SKILL.md
---
name: incident-command
description: Runs a production incident from declaration to blameless postmortem - SEV1-SEV4 levels with measurable criteria, the four roles (incident commander, comms, ops, scribe) and what each must and must not do, an update cadence per SEV with internal and customer templates, a timestamped decision log appended to the Release Dossier, a structured IC handoff, and a postmortem section with timeline, contributing factors, 5-whys per factor, and owned, dated action items. Use when someone says "we have an incident", "declare a SEV", "who is IC", "write the status update", "hand off the incident", "start the postmortem", or when a progressive-rollout gate aborts and impact continues. Do NOT use for the revert-or-fix decision itself - use rollback-or-roll-forward instead; for authoring standing service runbooks, use runbook-writer; for a routine on-call shift handoff with no active incident, use oncall-handoff; for a quick severity call on a single alert, use sev-triage; for a standalone postmortem with no Release Dossier, use postmortem-writer.
---
# incident-command
Incidents often run long for coordination reasons as much as technical ones: several engineers debug the same hypothesis, nobody tells support what to say, the person who knows the fix is answering questions in a DM, and afterwards nobody can reconstruct which change was made when. Incident command addresses this with explicit roles, a fixed communication rhythm, and a written decision log. Tied to a Release Dossier, the log lands next to the release plan that preceded it, so the postmortem starts from evidence instead of memory.
## SEV levels
Criteria are measurable so declaration is not a debate. Defaults to tune to your product:
| SEV | Any one of | Response |
|---|---|---|
| SEV1 | core flow (login, checkout, primary API) failing for 5% or more of requests for 5+ min; data loss or corruption confirmed; security breach with data exposure; full outage of a paid product | page IC and all roles now; customer-facing status within 30 min; exec notified |
| SEV2 | core flow degraded (error rate over 1% or p99 over 3x baseline) for 10+ min; a non-core feature fully down; a single large customer fully blocked; a confirmed bug writing incorrect data at a low rate | page IC and ops; comms role assigned; status page if customer-visible |
| SEV3 | non-core feature degraded; workaround exists; internal tooling down | owning team handles in hours; IC optional |
| SEV4 | cosmetic or no current customer impact; near miss | ticket; postmortem optional |
Rules: when unsure between two levels, pick the higher and downgrade later. The IC may change the SEV at any time and logs why. Declaring costs little; under-declaring costs an hour of uncoordinated work.
## Roles
| Role | Does | Does NOT |Click to play with sound.