← Back to Skills
DevOps & InfrastructureEngineeringPlatinum

Leading a post-incident review to improve future responses.

Incident Postmortem Facilitator

SRE best practices, Just Culture, safety science

38 activationsexpertv5.0

Best for

  • Leading blameless postmortems after production incidents to identify contributing factors and action items
  • Facilitating timeline reconstruction workshops for complex distributed system failures
  • Building organizational learning culture through structured incident analysis using SRE best practices
  • Training engineering teams on Cook's safety science principles and Dekker's Just Culture methodology

What you'll get

  • Comprehensive postmortem document with chronological timeline, MTTD/MTTR metrics, contributing factor analysis using Ishikawa diagrams, and prioritized action items
  • Facilitation guide for blameless review session with structured questions, safety science principles application, and follow-up tracking framework
  • Contributing factors analysis report distinguishing between proximate triggers, enabling conditions, and systemic vulnerabilities with improvement recommendations
Expects

Complete incident data including timeline, affected services, user impact metrics, response actions taken, and access to involved team members for facilitation sessions.

Returns

Structured postmortem documents with blameless analysis, contributing factor identification, prioritized action items, and systemic improvement recommendations following SRE methodology.

What's inside

You are a Site Reliability Engineering postmortem facilitator. You transform raw incident data into structured, actionable postmortem documents that drive systemic improvements and organizational learning. - You reject "root cause" framing entirely, instead identifying all contributing factors that ...

Covers

What You Do DifferentlyMethodologyWatch For
Not designed for ↓
  • ×Real-time incident response or emergency coordination during active outages
  • ×Performing technical root cause analysis or debugging specific system failures
  • ×Writing incident communication for external customers or stakeholders
  • ×Designing monitoring systems or implementing observability tools

SupaScore

89
Research Quality (15%)
9.25
Prompt Engineering (25%)
8.75
Practical Utility (15%)
8.75
Completeness (10%)
9
User Satisfaction (20%)
9
Decision Usefulness (15%)
8.75

Evidence Policy

Standard: no explicit evidence policy.

incident-postmortemblameless-culturesreincident-managementroot-cause-analysiscontributing-factorsaction-itemstimeline-reconstructiondevopssite-reliabilityincident-responselearning-organization

Research Foundation: 8 sources (2 official docs, 1 academic, 2 industry frameworks, 2 books, 1 web)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.

Version History

v5.03/25/2026

v5.5 distilled from v2 via Claude Sonnet

v2.02/23/2026

Pipeline v4: rebuilt with 3 helper skills

v1.0.02/15/2026

Initial release

Works well with

Need more depth?

Specialist skills that go deeper in areas this skill touches.

Common Workflows

Complete Incident Management Lifecycle

End-to-end incident management from initial response through blameless analysis to proactive resilience testing

© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice