skills.rest
bordenet
bordenetCOMMUNITY
Explore all skills by this author →
GitHub

failure-autopsy

Analyzes failures using 5-Why to extract patterns and document preventive actions for future improvement.

8|1|Updated Jan 24, 2026
Search Tags:#post-mortem#root-cause#pattern-detection#5-why#preventive-action
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill failure-autopsy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: failure-autopsy
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/observability/failure-autopsy
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill failure-autopsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem analysis identifies root causes of incorrect assumptions and failed approaches, producing actionable lessons and preventive actions.

Core Features & Use Cases

  • Root-cause analysis (5-Why) to uncover deeper issues behind a failure.
  • Pattern detection to spot recurring failure modes and systemic risks.
  • Preventive actions and retroactive updates to processes and skills.

Quick Start

Invoke the skill after a failed approach to generate a concise post-mortem, including the 5-Why chain, identified patterns, and recommended preventive actions.

Frequently Asked Questions about failure-autopsy

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

FAQPage Schema
How do I conduct a root-cause post-mortem after a failed debugging approach?▼

A root-cause post-mortem identifies why an approach failed by performing a 5-Why analysis to uncover incorrect assumptions, extracting failure patterns, and documenting preventive actions to stop recurrence across projects.

What is the best way to stop recurring misdiagnoses and regression issues in my projects?▼

To stop recurring misdiagnoses and regression issues, run a post-mortem analysis that detects repeating failure patterns and generates retroactive updates to your existing processes and skills.

When do I need a 5-Why analysis for post-mortem investigations?▼

You need a 5-Why analysis for post-mortem investigations when you must move beyond surface-level symptoms to uncover deeper systemic issues and incorrect assumptions behind a failed approach.

How do I extract failure patterns from a regression investigation?▼

Extract failure patterns from a regression investigation by analyzing the documented root causes of the failed approach to identify systemic risks and generate preventive actions for future improvements.

Can I use post-mortem analysis to update my development processes after a misdiagnosis?▼

Yes, post-mortem analysis applies to misdiagnoses by producing preventive actions and retroactive updates that directly modify and improve your existing development processes and skills.

What should a post-mortem include to prevent future root-cause recurrence?▼

A post-mortem should include a 5-Why analysis chain, identified recurring failure patterns, and documented preventive actions to effectively guide future improvements and prevent root-cause recurrence.

Related Skills

Explore More Software Engineering Skills→
rory-datarory-data

debugging-dags

Diagnose failed Airflow DAGs and provide root-cause remediation.

Community
Advanced
tduck1equacktduck1equack

break-loop

Analyze fixed bugs across five dimensions to prevent recurrence.

Community
Advanced
VoDaiLoczVoDaiLocz
24

root-cause-analysis

Analyze systemic issues using 5 Whys and Fishbone diagrams.

Community
Advanced
da-moonda-moon
1

gsd-debugger

Diagnose bugs with structured workflows for hypothesis testing and root-cause documentation.

Community
Advanced