openspec-bulk-archive-change

Batch archiving OpenSpec changes is done by selecting completed changes through a multi-select interface, validating their artifacts and delta specs, resolving codebase conflicts, and confirming the operation before moving them to date-stamped directories.

Yes, batch archiving OpenSpec changes detects capability-level conflicts across selected changes by inspecting delta specs and searching the codebase to determine which changes are actually implemented before applying an ordered sync.

To archive multiple OpenSpec changes before a release, collect active changes, review the consolidated status and conflict resolutions, validate task completion, then confirm the single batch archive operation to cleanly remove them from the active set.

Yes, you need the openspec CLI available, along with read and write access to the openspec/changes directory, to parse status JSON and delta specs and execute the batch archive operation.

When conflicting delta specs are found, the archive process inspects the delta specs and searches the codebase to determine which changes are actually implemented, then applies an ordered sync to resolve the collisions before archiving.

Yes, archived OpenSpec changes are preserved with their original metadata by moving them to date-stamped directories, ensuring implemented work is not accidentally lost during repository maintenance.