What problem does it solve? Archiving many completed OpenSpec changes one at a time is slow and error-prone, especially when several changes touch the same capability spec. 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 (success, skipped, failed). - Conflict detection and resolution: Detects when two or more changes modify the same capability spec path, inspects the codebase for implementation evidence, and applies delta specs in chronological order or skips unimplemented ones. - Verified spec sync: 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 user-auth spec, and archive everything with a single confirmation. ## Quick Start Ask the assistant to archive all completed OpenSpec changes at once and let it prompt you to select which changes to include.
