retrospectlisted

# /retrospect — Release retrospective with validation enforcement Run a structured retrospective on a shipped commit range (or single commit, or current session). Produces a 10-section markdown report with per-fix verdicts, validation status, action recommendations, and re-diagnosis when fixes failed. Writes findings to `knowledge/logs/retrospect/` and runs aria's standard intake. Source spec: `docs/specs/2026-05-03-retrospect-skill-design.md`. ## When to use - After a release ships and the bug is partially or fully unresolved - When the user reports a regression and a recent change set could be the cause - Before proposing another fix to a bug that's already been "fixed" once - As a soft-suggested response to user pushback ("review what you did," "are these changes necessary") ## Step 0: Inputs & Mode Detection Parse the invocation arguments. The first positional argument is the **scope keyword**; subsequent positional arguments are scope-specific. Seven scopes plus a no-args default: | Scope | Trigger | Backward-compat flag (still accepted) | Bundle source | |---|---|---|---| | **(no args)** | `/retrospect` | — | Auto-range: last push on current branch — `git log @{push}..HEAD` if upstream is set, else `git log -10` and ask user to confirm range | | **commit** | `/retrospect commit <hash>` | `--commit <hash>` | Single commit | | **range** | `/retrospect range <ref1>..<ref2>` | `--range <ref1>..<ref2>` | `git log <ref1>..<ref2>` | | **pr** | `/retrospect pr <num>` | `-