What problem does it solve? Archiving many completed OpenSpec changes one at a time is slow and error-prone, especially when parallel changes touch the same capability specs. This Skill batches the archive operation, detects spec conflicts between changes, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in one confirmed operation, with per-change status tracking for success, skip, and failure outcomes. - Conflict detection and resolution: Identifies when two or more changes modify the same capability spec path, inspects the codebase for implementation evidence, and applies delta specs in chronological order when both are implemented. - Spec sync verification: Syncs included delta specs into main specs and verifies ADDED, MODIFIED, REMOVED, and RENAMED requirements before moving any change into the archive directory. - Use Case: After finishing a sprint with five parallel feature changes, run the batch archive to review a consolidated status table, resolve a conflict on the identity/user-auth spec, and archive all ready changes with date-prefixed directory names. ## Quick Start Ask the assistant to archive all completed OpenSpec changes in this repository and confirm the batch when shown the status table.