postmortem

Distill failures into principles and preflight checks from logs or diffs.

Updated Sep 30, 2021
One-click install
npx skills add https://github.com/isymchych/accel-os --skill postmortem-isymchych
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/isymchych/accel-os/tree/main/ai/codex/skills/postmortem
Command: npx skills add https://github.com/isymchych/accel-os --skill postmortem-isymchych

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill a failure into a reusable principle and a preflight check to prevent recurrence and guide future work.

Core Features & Use Cases

  • Structured learning: converts incident details into a concise Mistaken assumption, Correct principle, Generalized finding, General rule, and Preflight check.
  • Guardrails for future work: generates a one-sentence preflight check that can be applied to similar tasks.
  • Documentation leverage: supports creating AGENTS.md and error-prevention guidelines for teams.

Quick Start

Input the event, failure, and intent, then generate a generalized finding, a prescriptive rule, and a concrete preflight check.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I write an incident postmortem that prevents future code regressions?

To write a preventive incident postmortem, you distill a failure into a reusable principle and a preflight check. This process converts incident details from logs or diffs into a mistaken assumption, correct principle, generalized finding, general rule, and preflight check to guide future work.

What is the best way to turn command history into actionable lessons learned?

Turning command history into lessons learned involves extracting details from logs, diffs, or command history to form a generalized finding and a prescriptive rule. This creates a structured learning document and generates a concrete preflight check to prevent similar wasted effort.

Can I generate guardrails and preflight checks for an existing failure analysis?

Yes, you can generate guardrails for an existing failure analysis by applying this process to postmortems. It produces a generic lesson and a one-sentence preflight check that serves as error-prevention documentation for similar tasks.

Does postmortem analysis work for wasted engineering effort or only code changes?

Postmortem analysis works for both code changes and wasted engineering effort. By analyzing the event, failure, and intent, it generates a generalized finding and a prescriptive rule that applies to regressions, code changes, and wasted effort alike.

How do I create error-prevention guidelines from a root-cause analysis?

You create error-prevention guidelines from a root-cause analysis by distilling the failure into a correct principle and a preflight check. This output can be directly leveraged to create AGENTS.md and error-prevention guidelines for teams.