openspec-bulk-archive-change

Batch archiving completed openspec changes involves selecting multiple active changes, validating their task completion and artifact states, and moving their directories into a dated archive folder in a single operation. This avoids repetitive single-change archives in monorepo workflows.

Conflict detection for openspec delta specs works by inspecting the delta specs and the repository codebase to determine which capability specs are actually implemented. It then identifies the correct application order to resolve conflicts before archiving.

To run bulk archiving for openspec changes you need the openspec CLI installed, repository file access for inspecting spec and code states, and permission to move change directories into an archive folder within your repository.

Yes, you can automatically sync capability specs while archiving completed openspec changes. The process applies automated spec syncing when appropriate, consolidating status gathering and conflict resolution before moving the change directories.

During the bulk archive process, the operation tracks successes, skips, and failures deterministically. Changes that fail validation or conflict resolution are skipped, allowing successful changes to archive without interrupting the batch operation.