incident-postmortem
/incident-postmortem
This skill should be used when the user shares an incident timeline, Slack/Teams thread, alert history, logs from an outage, or asks to "write a postmortem", "write an incident report", "RCA", "root cause analysis", "post incident review", "PIR", or "summarise this outage". Apply proactively after an incident investigation concludes.
- Author
- rawnaveen ↗
- Repository
- architect-dev-toolkit ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when the user shares an incident timeline, Slack/Teams thread, alert history, logs from an outage, or asks to "write a postmortem", "write an incident report", "RCA", "root cause analysis", "post incident review", "PIR", or "summarise this outage". Apply proactively after an incident investigation concludes.
Triggers from the description
Original author description
This skill should be used when the user shares an incident timeline, Slack/Teams thread, alert history, logs from an outage, or asks to "write a postmortem", "write an incident report", "RCA", "root cause analysis", "post incident review", "PIR", or "summarise this outage". Apply proactively after an incident investigation concludes.
How it works
- Procedure
- Template
SKILL.md preview
---
name: incident-postmortem
description: >
This skill should be used when the user shares an incident timeline, Slack/Teams thread, alert history,
logs from an outage, or asks to "write a postmortem", "write an incident report", "RCA", "root cause
analysis", "post incident review", "PIR", or "summarise this outage". Apply proactively after an
incident investigation concludes.
metadata:
version: "0.1.0"
---
# Blameless postmortem
## Procedure
1. Build a timeline (timezone stated, Australia/Sydney by default) from the sources: detection, escalation,
mitigation, resolution. Mark detection gap and time to mitigate.
2. Quantify impact: users/transactions affected, duration, SLO/error-budget burn, financial or regulatory
exposure.
3. Root cause with "5 whys" down to systemic causes (process, tooling, design), never a person.
Separate trigger, root cause and contributing factors.
4. What went well, what went poorly, where we got lucky.
5. Action items: each with owner role, priority, due date and type (prevent / detect / mitigate),
and measurable done criteria. Prefer automated guards over "be more careful".
## Template
```
# Incident <ID>: <title>
Severity: <SEV> Date: <date> Duration: <hh:mm> Status: Draft
## Summary (3 sentences)
## Impact
## Timeline
| Time | Event |
## Root cause and contributing factors
## Detection and response
## What went well / poorly / lucky
## Action items
| # | Action | Type | Owner | Priority | Due |
## Lessons learned
```
Use neutral language ("the deploy pipeline allowed", not "X forgot"). Flag missing data as open questions.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rawnaveen/architect-dev-toolkit | 100 | MIT |
| github/awesome-copilot | 100 | MIT |
| logly/mureo | 100 | Apache-2.0 |
| meyshad/skillforge | 100 | MIT |
| thisiskurubaran/DevSecOps | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| Kuan-AI-com/agent-skills | 90 | MIT |
| JayRHa/AgentSkills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 67578e425998 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100postmortem
Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved. - 100incident-postmortem-writer
Drafts blameless incident postmortems from communication channel timelines, alert data, status page updates, and verbal debriefs. Structures the narrative into timeline, impact assessment, root cause analysis (RCA), contributing factors, and action items with owners. Use when… - 95incident
Guide incident response, root cause analysis, and post-mortem documentation. Use when: production incident, outage response, post-mortem writing, RCA. Not for: designing retries and checkpoints before failure — use /durable; setting alert thresholds and Error Budget policy — use… - 100writing-postmortems
Use when writing a postmortem, incident report, or root-cause analysis after an outage, a defect that reached users, a data issue, or a near miss - or when turning an incident channel, alert log, or war-room thread into a durable document. Encodes the blameless framing, the… - 100incident
Structured incident response. Use when user reports an outage, production error, or says 'incident', 'something is down', 'users are affected'. Triage severity, contain blast radius, root-cause, document timeline, generate postmortem. - 100ywc-incident-postmortem
(ywc) Use when a production incident has occurred and you need a structured postmortem: timeline reconstruction, root cause analysis (5 Whys), impact assessment, prevention action items, and an optional sanitized client-facing report. Trigger phrases: "장애 회고", "장애 원인 분석", "사고…