openspec-bulk-archive-change

Bulk-archiving completed OpenSpec changes moves finished work to a date-stamped archive directory. Select the target changes, confirm the batch operation, and the system moves each change to an archive/YYYY-MM-DD-<name> path while preserving metadata.

Delta-spec conflicts are automatically detected during the bulk-archive process. The system evaluates codebase evidence to resolve these conflicts deterministically, ensuring each change is archived safely without losing critical specification details.

Yes, bulk-archiving preserves existing metadata. The operation safely moves changes to an archive folder while maintaining the .openspec.yaml file and all associated metadata, ensuring no configuration or project state is lost during the filesystem move.

Yes, the OpenSpec CLI is required to bulk-archive completed changes. The skill relies on the CLI and filesystem moves to transfer completed changes to a date-stamped archive path while preserving project structure and metadata.

You should archive completed changes when finished work starts cluttering your active workspace. Bulk-archiving keeps the codebase focused on active work, reducing noise from completed delta specs and maintaining clear project hygiene across multiple changes.

Yes, multiple completed OpenSpec changes can be archived in a single batch operation. Select the changes you want to archive, confirm the batch process, and each change is moved sequentially to its own date-stamped archive directory.