Post Mortem
Run a blameless review with a timeline, contributing causes and owned action items. Use when an incident, outage, missed launch or failed experiment needs a written review.
Install
/plugin marketplace add borghei/Claude-SkillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borghei/Claude-Skills --skill post-mortemgit clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skills/project-management/execution/post-mortem ~/.claude/skills/post-mortemPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Post-Mortem (Blameless Incident Review) ## Overview A post-mortem is a structured, blameless review held after an incident, outage, regression, missed launch, or failed experiment. The goal is not to assign fault but to learn how the system (people, process, code, and organization) produced the outcome, and to commit to durable changes that reduce the chance of recurrence. It follows the blameless post-mortem practice common in site reliability engineering, with systems-thinking sources listed under References. Where the companion `discovery/pre-mortem/` skill imagines failure before it happens, post-mortem learns from failure that already did. ## Core Capabilities - **Severity classification** — Sev 0-4 + near-miss thresholds, with post-mortem requirement and SLA per level - **Blameless facilitation** — five ground rules, the Dekker New View, hindsight/counterfactual removal, the Allspaw test - **10-section authoring** — header → summary → impact → timeline → what went well/wrong → factors → RCA → actions → lessons - **Root-cause analysis** — 5 Whys for clear chains, Causal Tree for multi-factor Sev 0/1/2; root-cause vs contributing-factor - **Action-item discipline** — single owner, real ticket, testable acceptance criteria, recurring completion audit - **Distribution & archive** — audience-appropriate formats; searchable, service-tagged archive ## When to Use
Details
- Skill name
post-mortem- Repository
- borghei/Claude-Skills
- Path
project-management/execution/post-mortem/SKILL.md- Repo updated
- 8 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Post Mortem skill do?
Run a blameless review with a timeline, contributing causes and owned action items. Use when an incident, outage, missed launch or failed experiment needs a written review.
How do I install the Post Mortem skill?
Claude Code plugin: /plugin marketplace add borghei/Claude-Skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Post Mortem popular?
It lives in borghei/Claude-Skills, which has 1,157 GitHub stars and 217 forks, and is included in 1 curated skill list.
Related skills
Cto Advisor
1.2kborghei/Claude-Skills
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.
Customer Success Manager
1.2kborghei/Claude-Skills
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
Financial Analyst
1.2kborghei/Claude-Skills
Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making
Quality Manager Qmr
1.2kborghei/Claude-Skills
Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech. Use for management reviews, quality objectives and KPIs, quality culture, and Notified Body / FDA inspection prep per ISO 13485 Clause 5.5.2.
Pm Onboarding
1.2kborghei/Claude-Skills
Builds a new PM's 30-60-90 day plan from a situation diagnosis: stakeholder map, 1:1 questions, early wins and a first PRD. Use when starting a PM job, moving to a new team, or taking on new scope.
Regulatory Affairs Head
1.2kborghei/Claude-Skills
Senior Regulatory Affairs Manager for HealthTech and MedTech. Use for regulatory strategy, FDA 510(k)/PMA/De Novo submissions, EU MDR CE marking, global market access, and regulatory intelligence.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.