postmortem

Generates five-section blameless postmortems for AI-agent conversations.

9|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/lmorchard/decafclaw --skill postmortem-lmorchard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/lmorchard/decafclaw/tree/main/src/decafclaw/skills/postmortem
Command: npx skills add https://github.com/lmorchard/decafclaw --skill postmortem-lmorchard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams perform blameless, systems-level postmortems of conversations to identify root causes and generate minimal, actionable fixes, preserving momentum while learning from failures.

Core Features & Use Cases

  • Structured anomaly reporting: produces a consistent five-section postmortem with an evidence-based root-cause analysis.
  • Actionable patches: suggests concrete, testable changes to artifacts (files, prompts, tooling) to prevent recurrence.
  • Vault integration: writes the final report to the vault and presents it inline for review.

Quick Start

Invoke the postmortem analysis on the current conversation (optionally supply a focus via ARGUMENTS) to generate a structured report.

Frequently Asked Questions about postmortem

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

FAQPage Schema
What is a blameless postmortem and how does it identify root causes?

A blameless postmortem is a systems-level analysis that identifies root causes of conversation missteps without focusing on individual fault. It produces an evidence-based, five-section report that proposes minimal, actionable fixes to prevent recurrence.

How do I conduct a root-cause analysis on an AI-agent interaction?

To conduct root-cause analysis on an AI-agent interaction, invoke the postmortem skill on the current conversation. It generates a structured report pinpointing root causes and suggesting concrete, testable changes to artifacts like prompts and tooling.

Can I focus my postmortem report on a specific conversation misstep?

Yes, you can focus your postmortem report by supplying specific arguments when invoking the analysis. This optional focus allows you to target particular anomalies or missteps within the broader conversation for a more tailored root-cause analysis.

Does the postmortem analysis automatically save the root-cause report?

Yes, the postmortem analysis automatically saves the root-cause report. It integrates with vault_write to persist the final five-section report in the vault, while also presenting the completed analysis inline for immediate review.

When should I use a blameless postmortem for product reviews?

You should use a blameless postmortem for product reviews when you need reflective analysis to prevent failure recurrence. It is ideal for learning cycles where identifying systems-level root causes and generating actionable patches preserves momentum.

What is the best way to generate actionable fixes from a conversation analysis?

The best way to generate actionable fixes from a conversation analysis is using a structured postmortem format. It enforces a five-section report that suggests concrete, testable changes to files, prompts, and tooling to resolve the identified root causes.