openspec-archive-change

To archive a completed OpenSpec change safely, the workflow validates artifact status, confirms task completion, and optionally synchronizes specs before moving the change into dated archive storage using the openspec CLI.

Archiving an OpenSpec change with unfinished tasks triggers a warning. The process inspects artifact status and task completion beforehand, alerting you to incomplete work before proceeding with the archive relocation.

Yes, you need the openspec CLI installed. This archival process relies on the CLI to handle change listing, status inspection, and the commands required to move completed changes into archive storage.

Yes, you can select a specific change. When no target change is provided, the workflow lists active OpenSpec changes, allowing you to inspect completion status and choose the correct one for archiving.

Spec synchronization is an optional step during OpenSpec change archiving. It checks the delta spec sync state before finalizing the workflow, ensuring your specifications remain updated prior to moving the change into the archive.

The best way to prevent naming collisions is using the built-in archive workflow, which creates a uniquely dated archive path for each change, preventing conflicts before moving the finalized OpenSpec change into storage.