Postmortem Writer

Generate blameless postmortem documents with timelines, Five Whys, and SMART action items.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/cdalsoniii/brightpath-coder --skill postmortem-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Postmortem Writer
Source: https://github.com/cdalsoniii/brightpath-coder/tree/main/.cursor/skills/postmortem-writer
Command: npx skills add https://github.com/cdalsoniii/brightpath-coder --skill postmortem-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive, blameless postmortem documents by synthesizing incident data, ensuring a consistent and data-driven approach to incident review.

Core Features & Use Cases

  • Automated Timeline Reconstruction: Gathers and organizes incident events from various system logs and data sources.
  • Root Cause Analysis: Employs structured methodologies like the "Five Whys" to identify contributing factors beyond single points of failure.
  • Action Item Generation: Creates SMART (Specific, Measurable, Assigned, Realistic, Time-bound) action items for systemic improvements.
  • Recurrence Detection: Checks against historical postmortems to identify recurring issues.
  • Use Case: After a critical S1 incident is resolved, this Skill can be invoked to automatically draft a postmortem report, analyze its causes, and propose actionable steps to prevent future occurrences.

Quick Start

Use the Postmortem Writer skill to write a postmortem for the payment outage on Feb 3.

Frequently Asked Questions about Postmortem Writer

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

FAQPage Schema
How do I generate a blameless postmortem after resolving an incident?

To generate a blameless postmortem, the Skill synthesizes incident data, reconstructs timelines from logs, identifies contributing factors using the Five Whys methodology, and creates SMART action items for systemic improvement.

What is the Five Whys methodology for root cause analysis in incident management?

The Five Whys methodology for root cause analysis identifies contributing factors beyond single points of failure by iteratively asking why an incident occurred, ensuring a blameless approach to systemic review.

How do I write SMART action items for preventing recurring incident issues?

To write SMART action items for preventing recurrence, this Skill analyzes incident detection and mitigation effectiveness, then generates Specific, Measurable, Assigned, Realistic, and Time-bound tasks for systemic improvements.

Can I use historical postmortems to detect recurring incident patterns?

Yes, you can detect recurring incident patterns by checking current incident factors against historical postmortems stored in the postmortems directory, ensuring recurring issues are identified and addressed.

What logs and data do I need to reconstruct an incident timeline for a postmortem?

Reconstructing an incident timeline requires read access to incident logs, alerts, and communication records to gather and organize events from various system data sources into a chronological sequence.

Does blameless incident management work for analyzing critical S1 outages?

Yes, blameless incident management works for analyzing critical S1 outages by automatically drafting postmortem reports, analyzing causes without assigning blame, and proposing actionable steps to prevent future occurrences.