openspec-bulk-archive-change

To archive multiple completed OpenSpec changes at once, run the bulk-archive command. It reads change statuses and archives completed items into date-stamped directories while preserving metadata for traceability.

Handling spec conflicts during bulk archival requires a conflict-aware tool that detects delta specs touching the same capability. This Skill identifies overlapping changes and guides you through resolution before completing the archival.

Yes, you need the OpenSpec CLI to batch archive completed changes. The Skill requires the CLI to read change statuses and specs, enabling safe bulk archival into date-stamped directories with metadata preserved.

OpenSpec bulk archival preserves change history for release management by creating date-stamped archives and retaining metadata. This approach keeps change history compact while ensuring full traceability of completed work.

Yes, you can use bulk archiving for projects with parallel OpenSpec changes. It applies to projects with multiple parallel changes, ensuring delta-spec consistency checks and safe archival across concurrent work streams.

If delta specs touch the same capability during OpenSpec archival, the Skill detects the conflict and guides resolution. This prevents inconsistent archives by ensuring overlapping changes are reconciled before completion.