data
Incident Postmortem
Turn timelines, logs, and notes into a blameless postmortem with root cause and preventive actions.
- · Builds a timeline
- · Separates triggers from root cause
- · Creates preventive action items
View SKILL.md
--- name: incident-postmortem description: Turn timelines, logs, and notes into a blameless postmortem with root cause and preventive actions. --- # Incident Postmortem ## When To Use Use after outages, degraded service, data incidents, or operational failures. ## What Claude Should Optimize For - Builds a timeline - Separates triggers from root cause - Creates preventive action items ## Workflow 1. Collect facts and timeline. 2. Identify customer and business impact. 3. Analyze contributing factors. 4. Write corrective actions with owners. ## Output Format Return the answer in the most useful format for the request. Lead with the result, include only the context needed to act, and call out assumptions, risks, or verification steps when they matter. ## Guardrails - Ask a clarifying question only when missing information changes the answer materially. - Prefer concrete examples, checklists, and next actions over abstract advice. - Keep the response concise unless the user asks for depth. - Do not invent facts, sources, metrics, or code behavior. ## Tags - incident - postmortem - operations - reliability
incidentpostmortemoperationsreliability