openspec-bulk-archive-change

Batch-select your completed changes and confirm the bulk archive operation to move them into the archive directory. The operation enforces spec synchronization and provides per-change status reporting during movement.

Yes, you can resolve spec conflicts automatically during bulk archiving. The operation detects conflicts by inspecting delta specs and the codebase, then applies automated resolution before completing the archival process.

Yes, bulk archiving OpenSpec changes preserves configuration files. The batch operation ensures that existing OpenSpec configuration files remain intact and untouched during the movement of changes into the archive.

If changes fail during a bulk OpenSpec archive, the operation provides per-change status reporting. This allows you to identify exactly which changes succeeded or failed during the batch archival process.

You need a bulk archive operation when managing parallel OpenSpec changes across a codebase. It enables batch selection, conflict detection, and automated resolution for multiple completed changes simultaneously.