spectra-verifylisted

## Claude fork context This generated Claude Code skill runs with `context: fork`. The rules in this section take precedence over the shared `verify` body below. When no change name is provided, run `spectra list --json` and consider only active changes with implementation tasks. Auto-select only when exactly one matching active change exists. If there are zero matching active changes or more than one matching active change, return the candidate list or empty-state message and ask the main thread to rerun `/spectra-verify <change-name>`. Do NOT ask an interactive selection question inside the fork. --- Verify that an implementation matches the change artifacts (specs, tasks, design). **Input**: Optionally specify a change name after `/spectra-verify` (e.g., `/spectra-verify add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. **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. **If no change name provided, prompt for selection** Run `spectra list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select (if this tool is not available, ask as plain text and wait for the user's response). Show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with