What is the primary focus of the postmortem-writing skill?

The skill is designed to help teams document technical incidents objectively to identify systemic root causes and preventive actions without assigning blame.

How does the skill help with Root Cause Analysis (RCA)?

It implements the '5 Whys' technique, guiding you to dig deeper into technical failures until the underlying systemic issue is identified.

Does this skill provide a specific template?

Yes, it provides a comprehensive Markdown template including sections for Duration, Severity, Timeline, Root Cause, Impact, and Action Items.

What does it mean for a postmortem to be 'blameless'?

It means the documentation focuses on how the system allowed an error to occur rather than pointing fingers at individuals, which encourages honest reporting and better fixes.

Postmortem Writing

Name: Postmortem Writing
Author: timequity

bytimequity

Aprendizaje y Documentación

Generates structured, blameless root cause analysis documentation to facilitate team learning and prevent incident recurrence.

Acerca de

The Postmortem Writing skill empowers developers to conduct thorough incident retrospectives using a standardized, industry-best-practice framework. It guides users through creating detailed timelines, conducting '5 Whys' root cause analysis, and documenting technical impacts while maintaining a strictly blameless culture. By transforming production failures into actionable insights, this skill helps engineering teams build institutional knowledge and implement systemic fixes that improve long-term service reliability.

Características Principales

Actionable remediation tracking with owners and due dates
Guided '5 Whys' methodology for deep-root cause analysis
0 GitHub stars
Standardized Markdown templates for consistent incident reporting
Comprehensive impact assessment including users, revenue, and data
Blameless culture framework focusing on systemic improvements

Casos de Uso

Standardizing the incident review process across multiple engineering teams
Conducting a deep-dive analysis after a high-severity service outage
Building an institutional knowledge base of past system failures and fixes

Acerca de

Características Principales

Actionable remediation tracking with owners and due dates
Guided '5 Whys' methodology for deep-root cause analysis
0 GitHub stars
Standardized Markdown templates for consistent incident reporting
Comprehensive impact assessment including users, revenue, and data
Blameless culture framework focusing on systemic improvements

Casos de Uso

Standardizing the incident review process across multiple engineering teams
Conducting a deep-dive analysis after a high-severity service outage
Building an institutional knowledge base of past system failures and fixes