skills.rest
nshaikhs
nshaikhsCOMMUNITY
Explore all skills by this author →
GitHub

postmortem

Identify root causes of organizational failures using the 5 Whys analysis.

Updated Apr 25, 2026
Search Tags:#retrospective#postmortem#root-cause-analysis#process-improvement#five-whys#lessons-learned#change-register
One-click install
npx skills add https://github.com/nshaikhs/claude-code-for-operators --skill postmortem-nshaikhs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/nshaikhs/claude-code-for-operators/tree/main/skills/executive-mentor/skills/postmortem
Command: npx skills add https://github.com/nshaikhs/claude-code-for-operators --skill postmortem-nshaikhs

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill provides a structured framework for post-mortems to analyze failures in a system, identify root causes, and capture actionable learnings to prevent recurrence instead of blaming individuals.

## Core Features & Use Cases

  • Step-by-step methodology: define the event, perform the 5 Whys, distinguish root cause vs contributing factors, identify warning signs, and build a change register with a verification plan.
  • Output-rich formats: provides a Post-Mortem Output Format template including events, timeline, root cause, contributing factors, warning signs, change register, and verification.
  • Use cases: post-mortems for projects, product launches, hiring decisions, or process failures; suitable for executive reviews and team retrospectives.

### Quick Start Define the Event clearly, then fill the TIMELINE and ROOT CAUSE sections using the provided template.

Frequently Asked Questions about postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a root-cause analysis after a project failure?▼

Conduct a root-cause analysis by defining the failure event, applying the 5 Whys methodology to distinguish root causes from contributing factors, and building a change register to prevent recurrence.

What is the 5 Whys methodology for process improvement?▼

The 5 Whys methodology is a retrospective technique used to drill down into organizational failures by repeatedly asking why an event occurred until the underlying root cause is identified for process improvement.

Can I use this post-mortem framework for hiring decisions and product launches?▼

Yes, this post-mortem framework applies to hiring decisions, product launches, and process failures by systematically documenting what happened, why it happened, and how to improve future outcomes.

What's the best way to document lessons learned in a team retrospective?▼

Document lessons learned in a team retrospective by conforming to a defined template that includes event definition, timeline, root cause, contributing factors, warning signs, and a formal change register.

How do I separate root cause from contributing factors in a postmortem?▼

Separate root cause from contributing factors by using the 5 Whys analysis to isolate the primary reason for the failure, while listing other conditions that enabled the event as contributing factors.

Related Skills

Explore More Education & Research Skills→
StudentCristianStudentCristian

nw-post-mortem-framework

Structure incident retrospectives with timelines, root-cause analysis, and action items.

Community
Advanced
Veloxia-agencyVeloxia-agency

postmortem

Analyze failed events and produce structured post-mortems with root causes and corrective actions.

Community
Advanced
haabehaabe

retrospective

Document lessons learned from completed delivery increments into memory artifacts.

Community
Intermediate
sngmdsngmd
3

okr-retrospective

Analyze OKR results, score achievement, and generate retrospective reports.

Community
Advanced