What problem does it solve? Archiving many completed OpenSpec changes one at a time is repetitive, and overlapping delta specs can silently conflict when merged into the main specs. This Skill batch-archives selected changes while detecting and resolving spec conflicts by inspecting the actual codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in a single confirmed operation, moving each to openspec/changes/archive/YYYY-MM-DD-<name>. - Conflict detection and resolution: Maps capabilities to the changes that touch them, then checks the codebase to decide which delta specs to sync and in what order. - Consolidated status reporting: Shows per-change artifact, task, and spec status in one table before confirmation, with warnings for incomplete work. - Use Case: After finishing several parallel feature changes (e.g., OAuth, JWT, and config updates), archive them all at once while ensuring the shared auth spec is merged in chronological order based on what is actually implemented. ## Quick Start Ask the assistant to bulk archive your completed OpenSpec changes and it will list active changes, let you pick which ones to archive, resolve any spec conflicts, and move them into the archive directory.