Postmortem

/em -postmortem — Honest Analysis of What Went Wrong

40 stars 11 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ArogyaReddy/alirezarezvani-claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ArogyaReddy/alirezarezvani-claude-skills --skill postmortem
Manual install
git clone --depth 1 https://github.com/ArogyaReddy/alirezarezvani-claude-skills.git /tmp/alirezarezvani-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/alirezarezvani-claude-skills/c-level-advisor/executive-mentor/skills/postmortem ~/.claude/skills/postmortem

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /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, reputational)?

Precision matters. "We missed Q3 revenue" is not precise enough. "We closed $420K in new ARR vs $680K target — a $260K miss driven primarily by three deals that slipped to Q4 and one deal that was lost to a competitor" is precise.

### Step 2: The 5 Whys — Done Properly
Read the full skill on GitHub

Details

Skill name
postmortem
Path
c-level-advisor/executive-mentor/skills/postmortem/SKILL.md
License
MIT
Repo updated
17 March 2026
Copies
Found in 2 GitHub repos

FAQ

What does the Postmortem skill do?

/em -postmortem — Honest Analysis of What Went Wrong

How do I install the Postmortem skill?

Claude Code plugin: /plugin marketplace add ArogyaReddy/alirezarezvani-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Postmortem popular?

It lives in ArogyaReddy/alirezarezvani-claude-skills, which has 40 GitHub stars and 11 forks.

Related skills

AWS Solution Architect

40

ArogyaReddy/alirezarezvani-claude-skills

Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.

DevOps & Cloud11

Ceo Advisor

40

ArogyaReddy/alirezarezvani-claude-skills

Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

Productivity & Notes11

Code Reviewer

40

ArogyaReddy/alirezarezvani-claude-skills

Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.

Software Development11

Marketplace Audit

42

robbyt/claude-skills

Display plugin versions from marketplace.json. Use when user asks to "audit versions", "show plugin versions", "list marketplace versions", or wants to see the current state of plugin versioning.

Other

Visual Search Array Generator

43

NeuroAIHub/awesome_cognitive_and_neuroscience_skills

Specifies display parameters, set sizes, target-distractor similarity, and randomization constraints for visual search experiments

Other

Marketplace Bump

42

robbyt/claude-skills

Bump a plugin version in marketplace.json using semantic versioning. Use when user asks to "bump version", "increment version", "release new version", or after making changes that warrant a version update.

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.