From godmode
Manages incident response: classifies SEV1-4 severity, builds timelines with evidence, performs 5 Whys root cause analysis, generates blameless post-mortems with action items and metrics. Outputs Markdown docs and git commits.
How this command is triggered — by the user, by Claude, or both
Slash command
/godmode:incidentgodmode/The summary Claude sees in its command listing — used to decide when to auto-load this command
# /godmode:incident Incident response and blameless post-mortem management. Classifies incidents by severity (SEV1-4), constructs precise timelines, performs root cause analysis, and produces actionable post-mortem documents with tracked action items. ## Usage ## What It Does 1. Classifies incidents by severity (SEV1-4) with defined response times and escalation rules 2. Builds timestamped timelines with evidence (logs, dashboards, deploy records) 3. Quantifies impact (users affected, duration, revenue, SLA consumption) 4. Performs root cause analysis using 5 Whys technique 5. Generat...
Incident response and blameless post-mortem management. Classifies incidents by severity (SEV1-4), constructs precise timelines, performs root cause analysis, and produces actionable post-mortem documents with tracked action items.
/godmode:incident # Interactive incident management
/godmode:incident --classify # Classify severity only
/godmode:incident --timeline # Build/update incident timeline
/godmode:incident --postmortem # Generate post-mortem from timeline
/godmode:incident --retro # Retrospective post-mortem for past incident
/godmode:incident --actions # List and track action items
/godmode:incident --metrics # Incident metrics dashboard
/godmode:incident --template # Output blank post-mortem template
docs/incidents/INC-<ID>-postmortem.mddocs/incidents/INC-<ID>-timeline.md"incident: INC-<ID> — <severity> — <title> (<status>)"| Level | Impact | Response Time |
|---|---|---|
| SEV1 | Complete outage, data loss, security breach | Immediate (< 15 min) |
| SEV2 | Major degradation, critical feature broken | < 30 min |
| SEV3 | Partial degradation, workaround available | < 2 hours |
| SEV4 | Cosmetic issue, minimal user impact | Next business day |
If resolved: /godmode:plan to schedule remediation work.
If active: Focus on mitigation, re-run when resolved.
/godmode:incident Production API returning 500 errors
/godmode:incident --retro Write post-mortem for Tuesday's database outage
/godmode:incident --actions Show outstanding action items from all post-mortems
/godmode:incident --metrics Show incident frequency and MTTR trends
npx claudepluginhub arbazkhan971/godmode/incident-reporterCreates structured incident reports with root cause analysis, timeline tracking, and action item management for post-mortem documentation.
/postmortemDrafts a blameless postmortem for a given incident by ID/name or the most recent significant incident within a time window, reconstructing timeline and root cause from connected incident management tools.
/incidentGuides incident response from detection through triage, mitigation, and resolution, then produces a structured post-mortem document. Supports severity flags and direct incident descriptions for rapid triage.
/postmortem-summaryGenerates a structured postmortem summary for a resolved Rootly incident, including timeline, root cause, impact, and action items.
/incident-responseOrchestrates multi-agent incident response: detect, triage, resolve, and learn from production incidents using structured SRE practices. Supports --severity flag.
/write-postmortemComprehensive postmortem with timeline, RCA, prevention, and action items.