postmortem

Conduct blameless postmortems with SQL-based verification queries.

16|3|Updated May 5, 2026

Search Tags:#documentation #verification #postmortem #root-cause-analysis #incident #blameless #incident-reporting

Ready to run

npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill postmortem-kevin-liu-01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/postmortem
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill postmortem-kevin-liu-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams document production incidents in a blameless, evidence-based format and track remediation actions.

Core Features & Use Cases

Structured incident templates with evidence collection, timelines, and impact assessments.
Verification plan generation with SQL queries to prove fixes.
Blameless postmortem culture: fosters learning and preventive improvements.

Quick Start

Describe the incident, collect evidence, and populate the postmortem template.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I conduct a blameless postmortem for a production outage?▼

A blameless postmortem resolves production outages through a four-phase process: Investigate, Write, Verify, and Remediate. It captures evidence, timelines, and impact assessments in a standardized template to drive corrective actions without assigning blame.

What is the best way to document root-cause analysis for security events?▼

Root-cause analysis for security events is documented using a structured incident template that records evidence and impact. This enforces a blameless culture and generates SQL-based verification queries to confirm that remediation fixes are effective.

How do I verify remediation actions after an incident report?▼

You verify remediation actions by generating explicit SQL-based verification queries during the postmortem process. These queries run against your data to confirm that the documented corrective actions successfully resolved the production incident.

Can I use a postmortem template for financial loss incidents?▼

Yes, the postmortem template applies to outages, degradation, financial loss, and security events. It provides a structured written record and verified remediation plan for any production incident requiring evidence-based corrective action.

What should be included in an incident report to prevent future outages?▼

An incident report should include collected evidence, a detailed timeline, impact assessments, and a verification plan with SQL queries. This standardized format fosters blameless learning and tracks explicit corrective actions to prevent future outages.

Does incident reporting work without assigning blame to engineers?▼

Yes, blameless incident reporting focuses on evidence-based documentation and preventive improvements rather than individual fault. It captures the root cause and corrective actions needed to resolve production incidents and foster team learning.