incident-postmortem

Name: incident-postmortem
Availability: InStock
Author: Flintmere

Generate a blameless post-mortem and append it to incident-history.md.

Updated Apr 18, 2026

Search Tags:#post-mortem #root-cause #incident #blameless #action-items #incident-history

Ready to run

npx skills add https://github.com/Flintmere/flintmere --skill incident-postmortem-flintmere

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/incident-postmortem
Command: npx skills add https://github.com/Flintmere/flintmere --skill incident-postmortem-flintmere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document incidents after resolution in a blameless, structured format and append a post-mortem to memory/product-engineering/incident-history.md to preserve institutional learning.

Core Features & Use Cases

Structured, blameless root-cause analysis documenting the incident timeline, contributing factors, customer impact, and action items with owners and due dates.
Append-only history entries that preserve original statements and allow follow-up corrections in separate entries.
Council-facing sign-off workflow ensuring alignment with operations, security, and engineering governance.

Quick Start

Follow the incident flow to document a resolved incident and append the post-mortem to memory/product-engineering/incident-history.md.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema

How do I document a blameless post-mortem after resolving an operations incident?▼

A blameless post-mortem documents the incident timeline, contributing factors, and customer impact without assigning blame. This Skill generates a structured root-cause analysis and appends it to your incident history file.

What is included in a structured root-cause analysis for incident history?▼

A structured root-cause analysis includes the incident timeline, contributing factors, customer impact assessment, and action items with assigned owners and due dates. It also requires council sign-off for finalization.

How do I track action items with owners and due dates after an incident?▼

You track action items with owners and due dates by generating a post-mortem document that structures these fields alongside the root-cause analysis. The workflow appends this data to your incident history.

Can I update an incident post-mortem after it has been appended to the history file?▼

Yes, the workflow uses an append-only history format that preserves original statements. You cannot modify existing entries, but you can add follow-up corrections in separate entries.

Does the incident post-mortem workflow require council sign-off for finalization?▼

Yes, the post-mortem workflow includes a council-facing sign-off process to ensure alignment with operations, security, and engineering governance before the incident entry is finalized.

What's the best way to maintain institutional learning from resolved operations incidents?▼

Maintaining institutional learning requires appending blameless post-mortems to a shared incident history file. This preserves the root-cause analysis and action items for future reference by engineering teams.