analyze-decisionlisted

# /analyze:decision Past-decision audit sub-command in the `/analyze` cluster. Loads and runs the [`decision-review`](../../../../skills/decision-review/SKILL.md) skill. ## Instructions ### 1. Identify the decision Ask the user (in their language) for: - The ADR identifier (e.g. `ADR-042`) or informal name. - The path to the ADR file, or the slug to look up in `docs/decisions/` or `docs/adrs/`. If the user names the decision informally, check the index before reading the full file. ### 2. Run the decision-review skill Delegate to [`decision-review`](../../../../skills/decision-review/SKILL.md) verbatim: 1. **Locate and read the full ADR** before proceeding. 2. **Restate** — chosen option, context then, assumptions, alternatives rejected. 3. **Compare to reality now** — for each assumption: held / broke / unknown, with evidence. List new information not available at decision time. 4. **Verdict** — one of three: - *Still valid* — document the validation date. - *Needs amendment* — core decision stands; recommend specific amendment. - *Superseded* — name the successor option; recommend `decision-record` + `adr-create` as the forward path. Hindsight discipline: judge each assumption against the information available at the time it was made, not against the outcome alone. ### 3. Memory write-back (dedup-first) Before drafting a new candidate, call `retrieve()` over the same key-space (decision area, affected paths) per [`analysis-memory-lo