optimization.postmortem

Generate standardized postmortem documents with root-cause analysis and corrective actions.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/edwardmonteiro/Aiskillinpractice --skill optimization-postmortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimization.postmortem
Source: https://github.com/edwardmonteiro/Aiskillinpractice/tree/main/skills/optimization/postmortem
Command: npx skills add https://github.com/edwardmonteiro/Aiskillinpractice --skill optimization-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes post-incident analysis, enabling engineering and reliability teams to rapidly document learnings, identify root causes, and implement corrective actions to prevent recurrence.

Core Features & Use Cases

  • Incident Timeline: Detail sequence of events with timestamps and decision points.
  • Root Cause Analysis: Perform analysis using techniques like 5 Whys or fishbone.
  • Use Case: Use this Skill to generate a postmortem for a "production outage" incident, detailing the timeline, identifying the primary cause (e.g., misconfiguration), and outlining steps to prevent future occurrences.

Quick Start

Use the postmortem skill for the "database connection failure" incident, impacting "all users, core services."

Frequently Asked Questions about optimization.postmortem

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

FAQPage Schema
How do I standardize postmortem documentation after an incident?

Postmortem standardization structures incident analysis across timeline, root cause, and corrective actions. This Skill automates generation of standardized postmortems from incident summaries, impact scope, and mitigation steps, producing formatted output that captures learnings and prevents recurrence.

What root cause analysis techniques does this postmortem process use?

Root cause analysis employs techniques like 5 Whys and fishbone diagrams to identify primary causes. The postmortem generation applies these methods to incident data, moving beyond surface symptoms to uncover systemic factors and assign corrective actions with owners and deadlines.

Can I use this for production outages and database incidents?

Yes, this Skill applies across incident types including production outages and database failures. It generates postmortems detailing timelines, impact on users and services, root causes like misconfigurations, and preventive measures to avoid future occurrences.

What incident information do I need to provide to generate a postmortem?

Provide incident summary, impact scope (affected users and services), incident duration, and mitigation steps taken. The Skill uses these inputs to automatically generate structured postmortem output covering impact timeline, root cause analysis, corrective actions, and preventive measures.

How does this help reliability and QA teams prevent incident recurrence?

Postmortem automation enables rapid documentation of learnings and systematic tracking of corrective actions with assigned owners and deadlines. This structured approach across engineering, reliability, and QA domains identifies patterns and implements preventive measures to reduce future incidents.