post-mortem-learning

Analyze failed deliveries and QA reports to identify root causes and extract lessons.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill post-mortem-learning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem-learning
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/post-mortem-learning
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill post-mortem-learning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand and learn from significant delivery failures or repeated quality issues by systematically analyzing what went wrong and why.

Core Features & Use Cases

  • Root Cause Analysis: Identifies the specific technical, contextual, or decision-making causes behind failures.
  • Failure Narrative Reconstruction: Creates a clear timeline and story of events leading to the failure.
  • Lesson Extraction: Distills raw, specific lessons learned directly from the failure event, avoiding generalizations.
  • Use Case: After a critical feature release fails QA multiple times, activate this skill to pinpoint the exact reasons for the repeated failures and extract actionable insights for the development team.

Quick Start

Analyze the recent delivery failure using the provided QA reports and context artifacts.

Frequently Asked Questions about post-mortem-learning

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

FAQPage Schema
How do I conduct a post-mortem analysis for a failed software delivery?

Conduct a post-mortem analysis by inputting failed story results, QA reports, and contextual artifacts to reconstruct the failure timeline, identify root causes, and extract specific lessons learned.

What is the best way to identify the root cause of repeated QA failures?

Identify the root cause of repeated QA failures by systematically analyzing quality assurance reports and contextual artifacts to map rule weaknesses and pinpoint exact technical or decision-making causes.

Can I use incident review techniques to extract actionable lessons learned?

Yes, you can use incident review techniques to distill raw, specific lessons learned directly from failure events by analyzing suboptimal deliveries and avoiding generalizations.

What inputs do I need to perform a failure analysis on a critical feature release?

Performing a failure analysis requires inputs of failed story results, QA reports, and contextual artifacts to accurately reconstruct events and identify contributing factors behind the release failure.

How does failure narrative reconstruction work for incident reviews?

Failure narrative reconstruction works by analyzing provided context artifacts and QA reports to create a clear timeline and story of events leading to the failure during an incident review.

What are the limitations of using post-mortem learning for quality assurance?

A limitation is that it avoids generalizations and requires specific contextual artifacts and QA failure data to accurately map rule weaknesses, meaning insufficient context limits the root cause analysis.