postmortem-skill

Generates blameless incident postmortems with timeline reconstruction, 5-Whys root-cause analysis, and tracked action items.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/innFactory-AI/company-ai-stack-skills --skill postmortem-skill-innfactory-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem-skill
Source: https://github.com/innFactory-AI/company-ai-stack-skills/tree/main/de/skills/engineering/postmortem-skill
Command: npx skills add https://github.com/innFactory-AI/company-ai-stack-skills --skill postmortem-skill-innfactory-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a production incident, teams struggle to reconstruct what happened, identify systemic root causes without blaming individuals, and produce actionable follow-ups. This Skill structures the entire postmortem process so nothing is missed and lessons actually stick. ## Core Features & Use Cases - Timeline Reconstruction: Builds a chronological UTC timeline from monitoring alerts, deployment records, chat logs, and user reports, separating observation from interpretation. - 5-Whys Root-Cause Analysis: Iteratively drills from symptom to systemic root cause, with evidence required at every step and support for branching causal chains. - Action Item Tracking: Generates prioritized action items (Fix, Detect, Mitigate, Prevent, Document) each with an owner, deadline, and verification method, and flags recurring uncompleted items from past postmortems. - Use Case: After a 45-minute checkout outage, feed the Skill your PagerDuty alerts, GitHub deploy history, and Slack incident channel logs to produce a complete blameless postmortem report with TTD/TTM/TTR metrics and assigned action items. ## Quick Start Run a postmortem for last night's checkout outage using the attached alert logs and deployment history.

Frequently Asked Questions about postmortem-skill

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

FAQPage Schema
How do I run a blameless postmortem after a production incident?▼

Provide the incident data (alerts, deploy history, chat logs) and trigger the skill with a phrase like "Postmortem durchführen für". It reconstructs a UTC timeline, runs a 5-Whys analysis, and produces a report with action items, owners, and deadlines.

What data sources does the postmortem skill use?▼

It can pull from MCP-connected tools like Datadog, Grafana, PagerDuty, GitHub, GitLab, Slack, Teams, Jira, and Linear, plus companyRAG collections or uploaded files. Without connected sources, you can paste the data directly into the chat.

How does the 5-Whys root cause analysis work here?▼

The skill iteratively asks why from the observable symptom down to an actionable systemic cause, requiring evidence for each step. It stops at system failures rather than blaming individuals and supports branching chains for incidents with multiple causal paths.

Can the postmortem skill handle incidents with incomplete data?▼

Yes. Unknown timeline times are marked as approximate, and if evidence is insufficient the report states "Root Cause unbestimmt" and lists what additional data is needed. It never fabricates events or root causes.

Does the skill track action items from previous postmortems?▼

Yes. Before finalizing, it checks earlier postmortems for similar uncompleted action items and escalates recurring ones as a systemic signal. Every new action item requires an owner, deadline, priority, and verification method.