openspec-bulk-archive-change

Batch-archiving completed OpenSpec changes moves multiple entries into a timestamped folder simultaneously. The process automates batch selection, resolves delta spec conflicts, and preserves original metadata while relocating changes.

Yes, batch archiving handles delta spec conflicts through conflict-aware syncing. It detects and resolves conflicts when delta specs exist across multiple changes, ensuring accurate archival of artifacts and tasks without losing data.

Yes, bulk archiving completed changes requires the OpenSpec CLI. The CLI manages batch selection, handles delta specs and artifacts, and executes the relocation into the date-stamped archive directory.

The best way to clean up a cluttered workspace is batch-archiving completed OpenSpec changes. It moves multiple parallel changes into a timestamped archive folder, preserving original metadata and providing a detailed operation log for traceability.

OpenSpec bulk archiving preserves metadata by retaining original change information during the move to a date-stamped directory. It also generates a detailed operation log, providing full traceability and auditing for the batch archival process.

Batch archiving encounters issues when parallel delta specs have unresolved conflicts. The skill includes conflict-aware syncing to detect and resolve these discrepancies during the archival of changes, ensuring a clean workspace history.