Skip to content
Back to skills

Post Mortem Learning

ASecurity

Analyze failures and suboptimal deliveries to identify root causes, contributing factors, and raw lessons. Activate after significant delivery failures, repeated QA failures, or when patterns of issues need to be understood.

  • 162 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsgotesting

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add digipulse-engineering/GAAI-framework --skill post-mortem-learning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Post Mortem Learning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Post Mortem Learning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/digipulse-engineering-post-mortem-learning/badge)](https://www.skillsdirectory.com/skills/digipulse-engineering-post-mortem-learning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: post-mortem-learning
description: Analyze failures and suboptimal deliveries to identify root causes, contributing factors, and raw lessons. Activate after significant delivery failures, repeated QA failures, or when patterns of issues need to be understood.
license: ELv2
compatibility: Works with any filesystem-based AI coding agent
metadata:
  author: gaai-framework
  version: "1.0"
  category: cross
  track: cross-cutting
  id: SKILL-POST-MORTEM-LEARNING-001
  updated_at: 2026-02-26
  status: experimental
inputs:
  - failed_or_degraded_story_results
  - qa_reports
  - contexts/artefacts/**  (delivered)
  - contexts/memory/decisions/**
  - contexts/rules/**  (applied)
outputs:
  - root_cause_analysis
  - contributing_factors
  - raw_lessons
  - failure_scenarios
  - improvement_candidates
---

# Post-Mortem Learning

## Purpose / When to Activate

Activate after:
- Significant delivery failures
- Repeated QA failures on the same area
- Delivery that missed its success metrics
- Patterns of issues that need systemic understanding

---

## Process

1. Reconstruct what happened end-to-end
2. Compare expected vs actual outcomes
3. Identify: technical causes, contextual gaps, decision errors, rule weaknesses
4. Produce concrete failure narratives
5. Extract **raw lessons (non-generalized)** — specific to this failure

---

## Outputs

- Root cause analysis report
- Failure timeline
- Mapped rule gaps
- Raw lesson list (specific, not generic)
- Candidate improvement areas (for backlog or rules)

---

## Quality Checks

- Root causes are specific, not generic ("insufficient testing" is invalid — "acceptance criterion #3 had no test coverage" is valid)
- Lessons are raw and specific, not platitudes
- Failure timeline is traceable
- Rule gaps link to specific rule files

---

## Non-Goals

This skill must NOT:
- Propose solutions (produces inputs for backlog and rules, not fixes)
- Assign blame
- Generalize into vague lessons

**Makes failures understandable and actionable. Enables serious continuous improvement.**

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.