What problem does it solve? Engineering teams often run postmortems that blame individuals, write action items that never get completed, and track delivery metrics that get gamed or misreported. This Skill provides structured guidance for running blameless incident reviews, writing actionable remediation items, and measuring delivery performance with DORA metrics so that incidents actually lead to systemic change. ## Core Features & Use Cases - Blameless Postmortem Framework: Reconstruct timelines before causal analysis, avoid counterfactual reasoning, and push past "human error" to changeable conditions. - Action Item Hygiene: Enforce single named owners, due dates, backlog integration, and completion-rate tracking so remediation work actually ships. - DORA Metrics With Precise Definitions: Measure deployment frequency, lead time from first commit, change failure rate, and recovery time using median and p85, derived from git, pipeline, and incident data. - Use Case: After a production outage, use this Skill to structure the postmortem, generate owned and dated remediation items classified by leverage (prevention vs. detection), and verify the team's DORA metrics are defined correctly. ## Quick Start Ask the assistant to help you write a blameless postmortem for a recent incident, including a timeline, root cause analysis, and owned action items.
