Incident post-mortem

1---
2name: "postmortem"
3title: "Incident post-mortem"
4description: "Structures a blameless post-mortem from an incident timeline."
5audience: "internal"
6format: "structured-doc"
7tone: "direct"
8triggers:
9  - "incident post-mortem"
10  - "blameless retro"
11  - "turn this timeline into a postmortem"
12---
13
14## Overview
15This skill handles **Incident post-mortem**. It produces structured doc output in a direct voice, written for internal team.
16When this skill is triggered, expect the user to provide: **Incident timeline, contributing factors, fixes, and follow-up notes**. If this input has not been provided, ask for it before proceeding — do not guess or use placeholder data.
17## Process
181. Summarise the incident impact, duration, and affected systems.
192. Lay out a factual timeline in chronological order.
203. Explain root causes and contributing factors without blame language.
214. Document the immediate fixes that resolved the issue.
225. List follow-up actions with owners and due dates.
23## Quality Standards
24- Use headings the team already recognises
25- Assign an owner to every action item
26- Flag blockers or risks with clear impact statements
27- Keep it under 500 words unless complexity demands more
28
29## What to Avoid
30
31- Do not speculate beyond the available evidence or assign blame to individuals.
32
33## Example Triggers
34- "incident post-mortem"
35- "blameless retro"
36- "turn this timeline into a postmortem"