openspec-bulk-archive-change

Batch archive multiple OpenSpec changes by selecting active changes and confirming the operation once. This streamlines project maintenance by applying safety checks, preserving metadata, and maintaining an organized archive directory.

Conflict detection for parallel changes is handled using delta specs and code evidence. The batch archival process checks for conflicts before archiving to prevent drift between related changes and ensure safe cleanup.

Spec syncing is required when implemented changes have modified the codebase. The batch archival process syncs these specs during the operation to ensure the archive reflects the final state before completing the cleanup.

Yes, the batch archival process preserves the .openspec.yaml configuration file. It maintains an organized archive directory while keeping all original metadata intact during the transition.

Batch archival reduces manual overhead by processing multiple changes in a single operation with one confirmation. It prevents drift between related changes and cleans up active change sets more efficiently than individual processing.

The batch archival requires a single confirmation before processing and enforces safety checks based on delta specs. Users must resolve any detected conflicts before the operation can proceed to archive the selected changes safely.