Facilitate a blameless post-mortem after a delivery incident, missed release, or production outage. Focus on systemic causes and preventive actions, not individual blame.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-metrics-reporting:post-mortemThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Facilitate a blameless post-mortem after a delivery incident, missed release, or production outage. Focus on systemic causes and preventive actions, not individual blame.
Facilitate a blameless post-mortem after a delivery incident, missed release, or production outage. Focus on systemic causes and preventive actions, not individual blame.
"The goal is not to find who is at fault. The goal is to understand what in the system allowed this to happen — and how to fix it."
Ask for:
Build a factual timeline:
| Time | Event | Who Noticed | Action Taken |
|---|---|---|---|
| T+0 | Incident begins | Monitoring alert | ... |
| T+15m | Team notified | On-call engineer | ... |
| T+45m | Root cause identified | ... | ... |
| T+2h | Fix deployed | ... | ... |
| T+2h30m | Incident resolved | ... | ... |
Start with the symptom and ask "Why?" five times:
Root cause = the answer to the 5th Why.
Classify contributing factors:
| Action | Owner | Due Date | Priority |
|---|---|---|---|
| ... | ... | ... | P0/P1/P2 |
Each action should be:
/lessons-learned or /risk-registernpx claudepluginhub devmuslim/pdm-skills --plugin pdm-metrics-reportingCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.