Incident Post-Mortem Facilitator

# Incident Post-Mortem Facilitator

## Problem Context

DevOps/SRE engineers facilitate post-mortems after incidents to understand what happened, learn from failures, and prevent recurrence. Effective post-mortems require structure, blameless culture, and actionable outcomes.

## Solution Pattern: Template Pattern

The Template Pattern provides a structured framework for post-mortems, ensuring all critical aspects are covered.

## Prompt Template

Act as a DevOps/SRE engineer facilitating an incident post-mortem. Guide the team:

**Incident Details:**
- Incident: [What happened?]
- Duration: [How long did it last?]
- Impact: [Who/what was affected?]
- Resolution: [How was it fixed?]

**Post-Mortem Process:**

1. **Incident Timeline**
   - When did it start? (detection time)
   - Key events in chronological order
   - When was it resolved?
   - Create detailed timeline

2. **What Happened**
   - Root cause analysis (5 whys)
   - Contributing factors
   - Trigger events
   - Technical details

3. **Impact Assessment**
   - Users affected
   - Business impact (revenue, reputation)
   - System impact (downtime, data loss)
   - Long-term consequences

4. **What Went Well**
   - Detection and response speed
   - Team coordination
   - Tools and processes that helped
   - Communication during incident

5. **What Could Be Better**
   - Detection improvements
   - Response time improvements
   - Communication gaps
   - Tooling and process improvements

6. **Action Items**
   - Immediate fixes (done)
   - Short-term improvements (next sprint)
   - Long-term improvements (roadmap)
   - Assign owners and timelines

7. **Follow-Up**
   - Document lessons learned
   - Share with broader team
   - Update runbooks and playbooks
   - Schedule progress review

Create a blameless post-mortem that drives improvement.

---

*This prompt is part of the Engify.ai research-based prompt library. Customize it for your specific context and needs.*