quality-postmortem

Analyzes escaped defects and test-suite health to produce actionable postmortems with owners and due dates.

64|12|Updated Mar 23, 2026

Search Tags:#qa #postmortem #root-cause-analysis #process-improvement #quality-metrics #blameless #test-suite-health

Ready to run

npx skills add https://github.com/petrkindlmann/qa-skills --skill quality-postmortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-postmortem
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/quality-postmortem
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill quality-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems identify systemic quality gaps exposed by escaped defects and incidents, turning them into concrete, trackable improvements.

Core Features & Use Cases

5 Whys root-cause analysis and blameless framing to surface systemic issues.
Action-item driven templates that assign owners and due dates, integrated with existing trackers.
Metrics and health reviews for test suites, flaky tests, and coverage to guide continuous improvement.

Quick Start

Start a postmortem by duplicating the template and filling in what happened, why, and what you will change to prevent recurrence.

Frequently Asked Questions about quality-postmortem

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

FAQPage Schema

How do I conduct a blameless postmortem for escaped defects?▼

A blameless postmortem analyzes escaped defects and test-suite health to surface systemic quality gaps. It uses 5 Whys root-cause analysis to identify issues and generates 1-3 concrete action items with assigned owners and due dates to prevent recurrence.

What is blameless postmortem framing in root-cause analysis?▼

Blameless framing in root-cause analysis focuses on systemic issues rather than individual mistakes. It applies 5 Whys methodology to exposed quality gaps, ensuring postmortems drive process improvement and trackable outcomes instead of assigning blame.

How do I track action items from a QA retro or postmortem?▼

Track action items by using action-item driven templates that assign specific owners and due dates to each improvement. This integration with existing trackers ensures 1-3 concrete tasks are generated per postmortem, driving continuous quality improvement.

Can I review test-suite health and flaky tests during a postmortem?▼

Yes, postmortems include metrics and health reviews for test suites, flaky tests, and coverage. Analyzing this test-suite health alongside escaped defects surfaces systemic quality gaps and guides opportunities for continuous improvement.

What's the best way to start a postmortem template for process improvement?▼

Start a postmortem by duplicating the template and filling in what happened, why it happened, and what you will change to prevent recurrence. Each postmortem must produce 1-3 concrete action items with owners and due dates, referencing related skills like qa-metrics and test-strategy.

When do I need a postmortem for quality metrics and test reliability?▼

You need a postmortem when escaped defects or incidents expose systemic quality gaps. Applying this across QA retros, postmortems, and test-reliability workflows turns identified issues into concrete, trackable improvements that drive action-oriented outcomes.