What problem does it solve?
Batch-archiving many completed openspec changes is error-prone and time-consuming when changes touch overlapping capability specs, have incomplete artifacts/tasks, or require intelligent spec synchronization based on actual implementation. This Skill centralizes validation, conflict detection, resolution, and archival so maintainers can safely retire multiple parallel changes in one operation.
Core Features & Use Cases
- Bulk discovery and selection: List active changes and let the user choose any number to process, including an "All changes" option.
- Automated validation: Gather artifact status, task completion, and delta spec contents for each selected change to build a consolidated readiness view.
- Conflict-aware spec sync: Detect capability-level conflicts, inspect the codebase to determine which change(s) are implemented, and apply spec syncs in resolved chronological order when appropriate.
- Safe archival workflow: Move changes into a dated archive folder while preserving metadata, report per-change outcomes (archived, skipped, failed), and continue processing despite individual failures.
- Use Case: A maintainer needs to archive ten completed feature changes at once while ensuring only implemented specs are merged and conflicts are resolved without manual code inspection.
Quick Start
Archive the selected completed changes, resolve any spec conflicts by inspecting the codebase, and return a summary of archived, skipped, and failed changes.
