Post-Mortem Analyst
Runs blameless 5-Whys retrospectives on failed launches, missed quarters, and bad hires.
- Repository
- alirezarezvani/claude-skills
- Stars
- 29,149
- Licence
- MIT
- Files
- 1 file
What it does
When you ask the agent to analyze a failure, it follows a structured, blame-free method: it pins down exactly what was expected versus what happened, digs past surface causes with a proper 5 Whys chain, separates root causes from contributing factors, and checks which warning signs were ignored. It ends with a change register of specific, owned, dated actions and a date to verify they worked. It is a text-based thinking framework; it does not look up any data itself.
Great for
- Leaders or managers reviewing a failed launch, missed revenue target, or bad hire
- Teams that want retrospectives to produce concrete fixes rather than vague action items
- People learning how to run a blameless root-cause analysis
Skip it if
- Legal, HR disciplinary, or compliance investigations, which need specialist process and professional advice; the skill is an analysis aid, not an authoritative inquiry
- Incidents that need live technical debugging, such as production outages, since the skill contains no technical diagnostic tools
Try asking
- “/em:postmortem the Q3 release that slipped six weeks”
- “/em:postmortem our failed enterprise deal with Acme last quarter”
- “/em:postmortem the product launch that got almost no adoption”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
postmortem.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip postmortem.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip postmortem.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Give the agent concrete facts up front, such as dates, dollar figures, and the expected versus actual outcome, so the analysis is precise rather than generic.
- Share the timeline and who raised which concerns; the warning-sign step depends on that context.
- Treat the output as a draft: check the root cause against your own knowledge and assign real owners before the change register is final.
What's inside
- SKILL.md
Redistributed unmodified from alirezarezvani/claude-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.