Incident Postmortem

Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Generates a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

What to give it

• Incident title / ID
• Severity — P1 / P2 / P3 or SEV1 / SEV2 / SEV3
• Date and duration — of the incident
• What happened — rough notes are fine — the skill will structure them
• Services or systems affected
• Customer impact — how many users, what was degraded
• How it was detected
• How it was resolved
• Initial thoughts on root cause
• Action items already identified (optional) — optional
• Responders — who was on-call or responded — names or roles; used for the timeline, not for blame
• Customer or external communications sent (optional) — optional — any status page updates, emails, or support messages with timestamps

Example output

Input: Checkout was down 42 minutes after a deploy set a wrong env var on the payments service; 5xx spiked, ~1,200 failed checkouts. Detected by alert in 6 min, fixed by rollback. Blameless postmortem with timeline and action items. · generated by claude-sonnet-4-6

Related skills