meta-retrolisted

## Procedure 1. Get the scratch directory: `!`scratch-dir.sh``. 2. Identify the retro type from $ARGUMENTS: - Incident: something broke, users affected, response happened - Sprint or iteration: time-boxed period of work - Feature or project: a shipped deliverable 3. Read $ARGUMENTS. If it references a file (timeline, postmortem draft, sprint notes): read it. 4. Pull git context if useful: `git log --since=<date>` for sprint retros. 5. Use the matching template below. ## Output file Write to `$(scratch-dir.sh)/retro-<type>-<slug>-<YYYYMMDD-HHMM>.md`. Print the path. ## Incident template ``` # Incident retro: <short name> ## Timeline <Minute by minute, detection through resolution. User impact at each step.> ## What happened <Plain language summary. Root cause vs contributing factors separated.> ## What went well <Detection speed, response coordination, tooling that helped.> ## What went poorly <Gaps in detection, response, communication, or tooling.> ## Lucky vs systemic <Separate "we caught it because X was awake" from "our system detected it". Lucky is not a control.> ## Action items <Each: description, owner by role (not name), priority, type (prevent, detect, respond, contain).> ## Followups deferred <Good ideas that are out of scope for this retro.> ``` ## Sprint or iteration template ``` # Sprint retro: <sprint label> ## What shipped <User-visible changes. Link to tickets.> ## What did not ship and why <Planned but deferred. Distinguish