openspec-bulk-archive-change

Batch archive completed OpenSpec changes by using a guided workflow that prompts for the target changes, validates their artifact status and task completion, and safely moves the change folders into the archive directory. This removes manual effort when closing several parallel feature branches.

Spec synchronization updates delta specs to ensure consistency before moving change folders into the archive tree. It inspects the codebase and implementation evidence to detect and resolve overlapping capability spec conflicts across parallel changes.

Yes, you need openspec CLI access to review active changes, validate task completion, handle delta spec conflicts, and execute the batch archive process. The CLI provides the necessary commands to interact with the spec archive directory.

When overlapping capability specs are detected during bulk archive cleanup, the workflow handles conflicts by inspecting the codebase and implementation evidence. It resolves these overlaps through agentic spec synchronization before moving the affected change folders.

Yes, the batch selection process explicitly prompts for the set of changes to archive instead of guessing or auto-selecting. This allows maintainers to choose specific completed feature branches while reviewing their readiness status and available delta specs.