npx skills add majiayu000/claude-skill-registry --skill postmortem-alirezarezvani-claude-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /em:postmortem — Honest Analysis of What Went Wrong **Command:** `/em:postmortem <event>` Not blame. Understanding. The failed deal, the missed quarter, the feature that flopped, the hire that didn't work out. What actually happened, why, and what changes as a result. --- ## Why Most Post-Mortems Fail They become one of two things: **The blame session** — someone gets scapegoated, defensive walls go up, actual causes don't get examined, and the same problem happens again in a different form. **The whitewash** — "We learned a lot, we're going to do better, here are 12 vague action items." Nothing changes. Same problem, different quarter. A real post-mortem is neither. It's a rigorous investigation into a system failure. Not "whose fault was it" but "what conditions made this outcome predictable in hindsight?" **The purpose:** extract the maximum learning value from a failure so you can prevent recurrence and improve the system. --- ## The Framework ### Step 1: Define the Event Precisely Before analysis: describe exactly what happened. - What was the expected outcome? - What was the actual outcome? - When was the gap first visible? - What was the impact (financial, operational, rep
- Why Most Post-Mortems Fail
- The Framework
- Step 1: Define the Event Precisely
- Step 2: The 5 Whys — Done Properly
- Step 3: Distinguish Contributing Factors from Root Cause
- Step 4: Identify the Warning Signs That Were Ignored
- Step 5: Distinguish What Was in Control vs. Out of Control
- Step 6: Build the Change Register
- Step 7: Verification Date
- Post-Mortem Output Format
- The Tone of Good Post-Mortems
What does the postmortem skill do?
/em -postmortem — Honest Analysis of What Went Wrong
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill postmortem-alirezarezvani-claude-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.