spectra-driftlisted

## Claude fork context This generated Claude Code skill runs with `context: fork`. The rules in this section take precedence over the shared `drift` body below. When no change name is provided, run `spectra list --json`. Auto-select only when there is exactly one active change. If there are zero active changes or more than one active change, return the candidate list or empty-state message and ask the main thread to rerun `/spectra-drift <change-name>`. Do NOT ask an interactive selection question inside the fork. --- Detect drift between a Spectra change and the current codebase state. Reports time dormancy, broken design anchors, task collisions with external commits, and a single recommended next command. **Input**: Optionally specify a change name (e.g., `/spectra-drift add-auth`). If omitted, infer from conversation context or auto-select if only one active change exists. **Prerequisites**: This skill requires the `spectra` CLI. If any `spectra` command fails with "command not found" or similar, report the error and STOP. **Steps** 1. **Determine change name** If not provided, infer from context or run `spectra list --json` to auto-select. If multiple active changes exist and no name is given, list candidates and ask the user to rerun with an explicit name. 2. **Run programmatic drift analysis** ```bash spectra drift <change-name> --json ``` The JSON contains: - `severity`: `"light"` / `"medium"` / `"heavy"` - `total_score`: aggregate ove