Incident Management
# Incident Management
The operational backbone of engineering reliability. These prompts cover the full incident lifecycle — from the moment an alert fires through to the organisational learning that prevents recurrence.
## When to Use These
- **Alert just fired:** Grab the incident commander runbook or the real-time status page update
- **During an incident:** Use the war room facilitation guide or the customer-facing comms template
- **After resolution:** Postmortem (see also Planning #11), remediation tracking, trend analysis
- **Proactively:** On-call handoff, runbook creation, incident readiness review, game day planning
## Prompts in This Category
| # | Prompt | When |
|---|--------|------|
| 01 | Incident Commander Runbook | When you're IC for a live incident |
| 02 | Real-Time Status Page Update | During an incident, communicating externally |
| 03 | Customer Apology Email | After a customer-impacting incident |
| 04 | War Room Facilitation Guide | Running the incident response call effectively |
| 05 | On-Call Handoff | Start/end of on-call rotation |
| 06 | Runbook Generator | Creating operational runbooks from tribal knowledge |
| 07 | Incident Trend Analysis | Quarterly review of incident patterns |
| 08 | Remediation Tracker | Tracking post-incident action items to completion |
| 09 | Severity Classification Guide | Defining P0-P4 for your org |
| 10 | Game Day Plan | Planning a chaos engineering or incident simulation exercise |
| 11 | Escalation Policy Document | Defining who to call, when, and how |
| 12 | Incident Readiness Review | Auditing your team's preparedness before a launch or migration |when to use it
Community prompt sourced from the open-source GitHub repo shiphrahx/AI-for-engineering-leaders (MIT). A "Incident Management" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
shiphrahx/AI-for-engineering-leaders · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions