openspec-bulk-archive-change

To batch archive openspec changes, use a prompt-driven multi-select to choose completed changes, then confirm the entire batch. The operation validates artifacts, syncs delta specs, resolves conflicts, and moves directories into a dated archive.

When delta specs conflict, the system inspects the codebase for implementation evidence and resolves conflicts by implementation status or chronological order, ensuring canonical specs reflect the actual implemented codebase state.

Spec sync occurs automatically during the batch archival process. After validation and conflict resolution, the tool optionally syncs delta specs to main specs while preserving metadata before moving change directories.

Archiving requires completed tasks and artifacts. The batch operation collects artifact status and task completion data for each change to determine readiness, skipping changes that fail these comprehensive validation checks.

The best way to clean up parallel change directories is a coordinated batch archive that detects capability conflicts, inspects implementation evidence, syncs specs, and tracks success, skips, and failures across the entire batch.

Bulk archiving requires conflict resolution because parallel changes often modify overlapping capabilities. Detecting and resolving these spec conflicts by implementation status or chronological order ensures the canonical specs accurately reflect the merged codebase.