optimization.postmortem
Produce a post-incident analysis capturing timeline, root causes, impact, and corrective actions.
$ 安裝
git clone https://github.com/edwardmonteiro/Aiskillinpractice /tmp/Aiskillinpractice && cp -r /tmp/Aiskillinpractice/skills/optimization/postmortem ~/.claude/skills/Aiskillinpractice// tip: Run this command in your terminal to install the skill
SKILL.md
name: optimization.postmortem phase: optimization roles:
- Engineering Lead
- SRE
- QA Lead
description: Produce a post-incident analysis capturing timeline, root causes, impact, and corrective actions.
variables:
required:
- name: incident_summary description: High-level summary of the incident.
- name: impact_scope description: Systems, users, or KPIs impacted. optional:
- name: duration description: Incident duration or timestamps.
- name: mitigation_steps description: Steps taken during mitigation. outputs:
- Incident timeline and contributing factors.
- Root cause analysis with classification and detection gaps.
- Corrective and preventive actions with owners.
Purpose
Standardize postmortem creation so engineering and reliability teams can rapidly document learnings and accountability.
Pre-run Checklist
- ✅ Gather incident alerts, logs, and chat transcripts.
- ✅ Confirm timeline with responders.
- ✅ Align on severity classification and stakeholders.
Invocation Guidance
codex run --skill optimization.postmortem \
--vars "incident_summary={{incident_summary}}" \
"impact_scope={{impact_scope}}" \
"duration={{duration}}" \
"mitigation_steps={{mitigation_steps}}"
Recommended Input Attachments
- Incident timeline exports (PagerDuty, Opsgenie, Slack).
- Monitoring dashboards or screenshots.
- Customer communications sent during the incident.
Claude Workflow Outline
- Summarize incident context, severity, impact, and timeline.
- Detail sequence of events with timestamps and decision points.
- Perform root cause analysis using techniques like 5 Whys or fishbone.
- Document detection gaps and monitoring improvements.
- Provide corrective and preventive actions with owners and deadlines.
Output Template
# Postmortem — {{incident_summary}}
## Impact & Timeline
- Severity:
- Impact Scope:
- Duration:
| Time | Event | Owner | Notes |
| --- | --- | --- | --- |
## Root Cause Analysis
- Primary Cause:
- Contributing Factors:
- Detection Gaps:
## Corrective Actions
| Action | Owner | Due Date | Status |
| --- | --- | --- | --- |
## Preventive Measures
- Monitoring Updates:
- Process Improvements:
- Follow-up Reviews:
Follow-up Actions
- Review postmortem in reliability or engineering forums.
- Track actions in the incident management system.
- Schedule follow-up to verify preventive measures are in place.
Repository

edwardmonteiro
Author
edwardmonteiro/Aiskillinpractice/skills/optimization/postmortem
0
Stars
1
Forks
Updated1d ago
Added1w ago