incident-commander

Installation
SKILL.md

Incident Commander

Run a production incident from declaration to post-incident review: set severity, coordinate response and comms, rebuild the timeline, and write a review whose action items prevent a repeat. The agent's judgment drives the live incident; the scripts score, structure and draft.

When to Use

  • An incident is active: decide severity, establish command, mitigate, communicate.
  • An incident is over: reconstruct the timeline, find root causes, assign action items.
  • Designing escalation paths, comms templates, response playbooks or SLA/error-budget policy.

Clarify First

Settle the inputs that change the work. When one is missing and would not change the result, use a sensible default and say which.

  • Active or post-incident? Active: ask only for impact (who and how many are affected, revenue, data or security exposure) and what is already being done, then give severity and the first comms. Do not start an RCA during an active incident.
  • Post-incident: the event sources (alerts, chat, deploys) and the format the organisation uses for reviews.
  • RCA method (post-incident only): 5 Whys for a single causal chain, Fishbone for many contributing factors, Bow Tie for safety/security-style incidents.

If the user wants a result straight away, produce it and state your assumptions at the top.

Installs
125
GitHub Stars
1.2K
First Seen
Feb 28, 2026