openspec-bulk-archive-change

Batch-archiving multiple OpenSpec changes requires the OpenSpec CLI to fetch active changes, run per-change status checks, detect delta-spec conflicts, and execute a consolidated archiving operation into the openspec/changes/archive/ directory.

No, batch archiving enforces non-auto-selection. You must manually guide the change selection process to validate each change's artifacts and tasks before confirming the final archiving operation.

Batch archiving detects delta-spec conflicts during the status check phase and resolves them autonomously by inspecting the codebase, ensuring consistent archiving while preserving original change metadata.

Yes, the OpenSpec CLI is required to perform batch archiving. You also need access to the repository's openspec/changes structure to validate artifacts, detect conflicts, and move completed changes to the archive.

Use the batch archive flow to consolidate multiple changes into a single operation. It preserves change metadata and generates a consolidated result report summarizing outcomes for record-keeping and release management.

Status checks validate each change's artifacts and tasks before archiving to ensure only completed changes are moved. This prevents incomplete work from being archived and surfaces delta-spec conflicts early in the batch operation.