Does this follow industry SRE standards?

Yes, the templates and methodologies provided are aligned with Site Reliability Engineering (SRE) best practices established by organizations like Google and Etsy.

How does this skill help with follow-up actions?

The skill provides a structured action item matrix that ensures every identified systemic gap is translated into a prioritized ticket with a clear owner and due date.

When should I use the 5 Whys analysis template?

The 5 Whys template is best used when you need to look beyond the immediate technical trigger to uncover the underlying organizational or architectural reasons why an incident occurred.

What is a blameless postmortem?

A blameless postmortem is an incident review process that focuses on identifying systemic conditions and process failures rather than individual mistakes, fostering a culture of psychological safety and learning.

Postmortem Writing & Incident Review

Name: Postmortem Writing & Incident Review
Author: drgaciw

bydrgaciw

생산성 및 워크플로

Generates comprehensive, blameless postmortem documents and root cause analyses to drive organizational learning after system incidents.

소개

This skill provides a structured framework for conducting incident reviews and creating detailed postmortem documentation within the Claude Code environment. It helps teams transition from a culture of blame to systemic improvement by facilitating deep root cause analysis, identifying contributing factors, and establishing actionable follow-up items. Whether handling a critical SEV1 outage or a minor near-miss, the skill offers specialized templates—including Standard Postmortems, 5 Whys Analysis, and Quick Reviews—alongside facilitation guides to ensure every incident results in measurable system resilience and team growth.

주요 기능

Facilitation guides for running effective post-incident review meetings
Actionable follow-up item generation with priority and ownership tracking
0 GitHub stars
Multi-tier postmortem templates for various incident severities
Blameless root cause analysis (RCA) frameworks and 5 Whys methodologies
Structured incident timeline construction and customer impact assessment

사용 사례

Conducting deep-dive reviews for critical service outages and data loss events
Facilitating systemic learning sessions to uncover architectural vulnerabilities
Standardizing incident reporting processes across engineering and DevOps teams

소개

주요 기능

Facilitation guides for running effective post-incident review meetings
Actionable follow-up item generation with priority and ownership tracking
0 GitHub stars
Multi-tier postmortem templates for various incident severities
Blameless root cause analysis (RCA) frameworks and 5 Whys methodologies
Structured incident timeline construction and customer impact assessment

사용 사례

Conducting deep-dive reviews for critical service outages and data loss events
Facilitating systemic learning sessions to uncover architectural vulnerabilities
Standardizing incident reporting processes across engineering and DevOps teams