retrospectivelisted

# Retrospective Turn execution experience into institutional knowledge. This skill orchestrates a fixed Phase 0 through Phase 5 workflow that gathers evidence, generates insights, diagnoses root causes, decides actions, scores atomicity, and persists learnings. The long-form rubrics live verbatim in `references/`; this file is the orchestration contract. This skill replaces the former `retrospective` agent (`.claude/agents/retrospective.md`). Lifecycle hooks can invoke a skill but not an agent, so the retrospective workflow moves here to be callable from `Skill("retrospective")`, from `/retro fill <date>` (Issue #2079), and from the Stop-hook auto-retrospective path (`.claude/hooks/Stop/invoke_auto_retrospective.py`). ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `run a retrospective` | Full Phase 0..5 workflow over the given scope | | `retro fill` | Fill an unfilled auto-retro skeleton for a date | | `extract learnings from this session` | Phase 0..4 over the current session | | `diagnose this failure` | Phase 0..2 root-cause analysis, then stop | | `what did we learn` | Phase 4 atomicity-scored learning extraction | --- ## When to Use | Situation | Use This Skill? | |-----------|-----------------| | Session ended with meaningful work and you want learnings persisted | Yes | | An unfilled auto-retro skeleton exists in `.agents/retrospective/` | Yes (fill it) | | Diagnosing why a task failed (Five Whys, fishbone) | Yes | | Capturing a sing