openspec-bulk-archive-change

To batch archive completed changes, select active changes via the OpenSpec CLI and confirm the batch operation. The tool validates statuses, resolves delta spec conflicts, preserves provenance like .openspec.yaml, and moves changes to an archive folder safely.

Spec conflict resolution during bulk archiving inspects delta specs and code evidence to detect conflicts in openspec/changes. It resolves them based on chronological order and code evidence, ensuring only eligible changes are archived while preserving original metadata.

Yes, batch archiving completed changes requires the openspec CLI and access to the repository. The CLI scans active changes, validates statuses and tasks, and executes the batch move into the archive folder while preserving provenance.

The bulk archive process ensures only eligible changes are archived by inspecting each active change's status, tasks, and delta specs. It validates completion criteria before allowing the batch operation to move changes into the archive folder.

When archiving completed changes in bulk, provenance is preserved by retaining original metadata including .openspec.yaml files. The tool moves changes to an archive folder while maintaining the full history and spec context of each archived change.

Delta spec conflicts occur when multiple changes modify the same specs. The bulk archive tool detects these conflicts by scanning openspec/changes, resolves them using code evidence and chronological order, and prevents archiving changes with unresolved conflicts.