openspec-bulk-archive-change

To batch archive OpenSpec changes, run the batch-archive command in your OpenSpec workspace. It analyzes active changes, detects delta spec conflicts, and moves eligible changes into a date-stamped archive folder while preserving .openspec.yaml metadata.

When delta spec conflicts are detected during OpenSpec archiving, the skill identifies the conflicting changes and outlines resolution strategies before proceeding. The batch operation provides a clear summary indicating which changes were archived, skipped, or failed due to these conflicts.

Yes, OpenSpec batch archiving preserves .openspec.yaml metadata for each change. The skill moves completed changes into the openspec/changes/archive directory under a date-stamped folder while ensuring this essential configuration file remains intact.

You can review the status of multiple archived OpenSpec changes by checking the generated summary provided after the batch operation. This summary enforces per-change status reporting, detailing whether each change was successfully archived, skipped, or failed.

Yes, you can archive several parallel OpenSpec changes together without losing audit history. The skill batches multiple completed changes into a dated archive folder, maintaining consistent and auditable archival history while providing a comprehensive summary of the operation.