openspec-archive-change

To archive completed OpenSpec changes safely, you validate artifact completion, task status, and delta-spec synchronization before moving the changeRoot into a structured, date-stamped archive directory to preserve provenance.

When archiving an OpenSpec change with incomplete tasks or artifacts, the process prompts you to address the missing items before proceeding, ensuring only fully validated and synchronized changes are moved into the archive.

The OpenSpec archive process prevents naming conflicts by creating a date-stamped, collision-checked archive path under the planningHome.changesDir/archive directory, ensuring each archived change receives a unique location.

Yes, you need the OpenSpec CLI environment to archive completed change artifacts, as the process requires its infrastructure to validate status JSON, determine readiness, and execute the changeRoot relocation.

Delta-spec synchronization assessment verifies that your change specifications are fully aligned before archiving, ensuring the archived artifacts accurately reflect the final state of your completed workflow planning.

If you do not provide a change name, the archiving workflow prompts you to select from active changes across your projects, guiding you through the validation and relocation process for the chosen item.