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). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.
▸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
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Timeline has no blame-focused language
✓Root cause is specific (not "human error")
✓Root cause answers "why did this happen?" not just "what happened?" — it names a system or process gap, not a symptom
✓Contributing factors explain the systemic gaps
✓Every action item has an owner and due date
✓"What went well" section is genuine, not token
✓No action item contains vague language like "improve monitoring", "increase resilience", or "better testing" — each must name a specific change
✓Executive summary is readable by non-technical leadership
⚠️ What it refuses to do
Do not assign blame to individuals — postmortems must focus on system and process failures
Do not write action items with vague language like "improve monitoring" — each must name a specific, ownable change
Do not skip the contributing factors — root cause alone misses the systemic issues that enable incidents
Do not omit the detection timeline — how long it took to detect matters as much as how long it took to resolve
Do not treat the postmortem as closed until all action items have named owners and due dates
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 -p pm-claude-skills pm-claude-skills-mcp
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