postmortemlisted
Install: claude install-skill harshitt13/Silicon-Valley-Skill
# Postmortem
Source: `$ARGUMENTS`
Empty means the conversation so far. A path means read that file. Anything else is the incident, as told.
## Gather
Pull out: when it started, when it was detected, when it was mitigated, when it was resolved; what users saw; what changed before it started; what was tried, in order; what finally worked. Anything not in the source is "unknown". Never fill a gap with a plausible fact. If a single missing timestamp changes the story, ask for it, once.
## Rules
- **Blameless.** Causes are conditions, systems, and decisions that made sense at the time. A person's name never appears as a cause. "The deploy went out without the migration" is a cause. "Alex forgot the migration" is a firing.
- **The root cause is usually boring.** Say the boring one: the config, the missing timeout, the retry without idempotency, the expired certificate. A dramatic root cause is usually a contributing factor in a costume.
- **Action items are few, specific, owned, and dated.** Three to five. Each maps to a contributing factor. "Improve monitoring" is not an action item. "Alert when checkout 5xx exceeds 1% for 5 minutes. Owner: name. By: date." is.
- **Detection time matters as much as fix time.** If the customer found it first, say so.
## Write it
Markdown, these headings, this order. No preamble before it, no remarks after it.
```
# Postmortem: <one-line title>
**Status:** draft
**Severity:** <sev, or unknown>
**Duration:** <start to resolved, or unknown>