skills.rest
jmigrala
jmigralaCOMMUNITY
Explore all skills by this author →
GitHub

postmortem

Guide teams through a six-step postmortem framework with root-cause analysis and change registers.

Updated Oct 30, 2025
Search Tags:#learning#retrospective#postmortem#root-cause#process-improvement#blame-free#change-register
One-click install
npx skills add https://github.com/jmigrala/priceyourfence --skill postmortem-jmigrala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/jmigrala/priceyourfence/tree/main/.agents/skills/executive-mentor/skills/postmortem
Command: npx skills add https://github.com/jmigrala/priceyourfence --skill postmortem-jmigrala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Postmortems are essential for learning from failures, but they often devolve into blame or vague optimism. This Skill provides a rigorous, blame-free framework to analyze what happened, why it happened, and how to prevent recurrence.

Core Features & Use Cases

  • Structured six-step framework: Define the Event, apply the 5 Whys, distinguish root cause from contributing factors, identify warning signs, separate in-control vs out-of-control factors, and build a change register with owners and timelines.
  • Blame-free retrospectives: Emphasizes learning over fault-finding and promotes organizational improvement.
  • Actionable outcomes: Produces concrete changes with owners, due dates, and verification plans to ensure follow-through.

Quick Start

Document the event, analyze root causes with the 5 Whys, and create a change register with owners and verification dates.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I run a blame-free postmortem after a failed deal or missed milestone?▼

A blame-free postmortem uses a structured six-step framework to analyze failed deals or missed milestones, focusing on learning over fault-finding to identify root causes and prevent recurrence.

What is the 5 Whys root-cause analysis technique used in retrospectives?▼

The 5 Whys root-cause analysis technique repeatedly asks why an event occurred to distinguish the core root cause from contributing factors, ensuring retrospectives address underlying systemic issues rather than surface-level symptoms.

How do I create a change register with owners and verification dates for process improvement?▼

To create a change register for process improvement, document concrete changes, assign specific owners, set due dates, and establish verification plans to ensure actionable outcomes and accountability for preventing future failures.

Can I use a structured retrospective framework for feature disappointments and out-of-control factors?▼

Yes, a structured retrospective framework analyzes feature disappointments by separating in-control factors from out-of-control factors, helping teams focus their change register on elements they can actually influence and improve.

What is the best way to identify warning signs before a project failure happens?▼

The best way to identify warning signs is to conduct an honest postmortem with a dedicated warning-sign check step, analyzing past failures to document early indicators and add them to a change register for proactive monitoring.

Related Skills

Explore More Content & Communication Skills→
ElliotJLTElliotJLT
60

retrospective

Document post-task reflections with sections for failed attempts, what worked, and learnings.

Community
Basic
Veloxia-agencyVeloxia-agency

postmortem

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

Community
Advanced
zm2231zm2231

stakeholder-communication

Create stakeholder maps and tailored communication plans for team initiatives.

Community
Advanced
borgheiborghei
467

scrum-master

Facilitate Scrum ceremonies and coach teams through agile practices.

Community
Basic