Postmortem and Learning Extractor

Purpose

Converts failures into fuel for the system's evolution. It ensures that the same mistake is never made twice by codifying lessons into skills, specs, or orchestration rules.

When to use this skill

• After an incident or production bug
• After a failed migration attempt or rejected PR
• After the completion of a major delivery to document "what went right"

Extraction Steps

1. Identify Root Causes: Use the "5 Whys" method to get past surface-level symptoms.
2. Separate Failure Types:
   • System Failure: A skill or orchestration rule was missing or flawed.
   • Human Failure: Approval was given to a flawed plan or spec.
3. Extract Reusable Rules: What instruction could be added to a SKILL.md to prevent this?
4. Update Specs or Skills: Trigger the appropriate update skill (e.g., skill-evolution-engine).