What problem does it solve? Archiving many completed OpenSpec changes one by one is slow and error-prone, especially when several changes touch the same capability spec. This Skill batches the whole operation: it collects status for every selected change, detects spec conflicts, resolves them by checking the codebase for actual implementations, and archives everything in a single confirmed pass. ## Core Features & Use Cases - Batch archiving: Select any number of active changes (1+ works, 2+ is typical) and archive them together with one confirmation. - Conflict detection and resolution: When two or more changes modify the same capability spec path, the Skill inspects the codebase to decide which delta specs to sync, applying both in chronological order when both are implemented. - Verified spec sync: Before moving any change into the archive directory, it runs the openspec-sync-specs workflow inline and verifies that ADDED, MODIFIED, REMOVED, and RENAMED requirements landed correctly in the main specs. - Use Case: After a sprint where five parallel changes (add-oauth, add-jwt, schema-management, project-config, add-verify-skill) were completed, run this Skill to review a consolidated status table, resolve the identity/user-auth spec conflict, and archive all ready changes at once. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and confirm the batch when the status table is shown.
