openspec-bulk-archive-change

Batch archiving changes allows you to select multiple completed changes and confirm a single operation that validates statuses, resolves delta spec conflicts, and moves records into an archive path for traceability.

Conflict resolution in bulk archiving identifies overlapping delta specs across multiple changes, inspects the codebase, and applies deterministic ordering to synchronize specs. This ensures archived changes do not contain conflicting delta specifications.

Yes, the openspec CLI is required to batch archive changes. The workflow uses the CLI to prompt for change selection, validate statuses, resolve spec conflicts, and move archived changes into an archive path.

The best way to manage parallel changes is bulk archiving completed changes, which validates statuses and resolves delta spec conflicts before moving records to an archive path. This preserves a traceable archive of past work while keeping active history focused.

You should avoid batch archiving changes when delta specs have unresolved conflicts or when changes lack completed statuses. The process validates statuses and applies deterministic ordering, so unmerged or active changes will fail validation and disrupt the batch archive operation.