openspec-bulk-archive-change

To bulk-archive OpenSpec changes, select completed changes via user prompts, and the system moves them into time-stamped archive directories while preserving original metadata and resolving delta-spec conflicts intelligently.

Conflict-aware spec synchronization detects delta-spec conflicts across selected changes by comparing them, then resolves those conflicts according to codebase evidence before the changes are archived.

Archiving preserves traceability by keeping the original .openspec.yaml intact and storing each archived change under archive/YYYY-MM-DD-<name>/, ensuring historical work remains auditable.

Yes, for workflows managing parallel changes, the system requires user prompts for selective archiving, allowing you to choose specific completed changes to archive rather than processing all changes blindly.

The best way to organize conflicting historical changes is batch-archiving them with conflict-aware syncing, which compares delta specs, resolves conflicts using codebase evidence, and stores results in time-stamped directories.

You should avoid bulk archiving when changes are not yet completed or when delta-spec conflicts cannot be resolved by codebase evidence, as the process is designed for finalizing and organizing finished historical work.