openspec-bulk-archive-change

Batch-archive completed OpenSpec changes by selecting multiple active changes, automatically detecting delta-spec conflicts, and moving them into date-stamped archive folders while preserving .openspec.yaml metadata.

During OpenSpec change archival, delta-spec conflicts are detected by examining the delta specs and codebase, allowing the batch process to automatically resolve conflicts or report detailed outcomes for each conflicting change.

Yes, you can archive multiple OpenSpec changes simultaneously without manual checks. The process automatically assesses readiness, detects overlapping delta specs, and handles conflict resolution across all selected changes.

OpenSpec batch archival preserves .openspec.yaml metadata by moving completed changes into archive/YYYY-MM-DD-<name> directories, ensuring configuration and tracking data remain intact during the release preparation workflow.

Streamline release preparation by using batch archival to validate active changes, resolve delta-spec conflicts, and consolidate completed changes into date-stamped archive folders in a single automated operation.

Batch-archiving OpenSpec changes encounters issues when delta specs overlap because conflicting changes cannot be safely archived. The tool identifies these conflicts by examining the codebase and reports outcomes for each affected change.