openspec-bulk-archive-change

Archive multiple completed changes in a single operation. This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented. **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root. **Input**: None required (prompts for selection) **Steps** 1. **Get active changes** Run `openspec list --json` to get all active changes. If no active changes exist, inform user and stop. 2. **Prompt for change selection** Use **AskUserQuestion tool** with multi-select to let user choose changes: - Show each change with its schema - Include an option for "All changes" - Allow any number of selections (1+ works, 2+ is the typical use case) **IMPORTANT**: Do NOT auto-select. Always let the user choose. 3. **Batch validation - gather status for all selected changes** For each selected change, collect: a. **Artifact status** - Run `openspec status --change "<name>" --json` ...