openspec-archive-change

You can archive completed OpenSpec changes by validating artifact completeness and task status, optionally synchronizing delta-specs, then moving the change directory into openspec/changes/archive/YYYY-MM-DD-<name>.

Archiving experimental changes in an OpenSpec workflow involves selecting a completed change, verifying artifact completion and task status, assessing delta-spec synchronization, and moving the directory into a dated archive path to preserve metadata.

Yes, you need the OpenSpec CLI to archive a completed change directory, along with access to openspec/changes and delta-specs where present, to determine synchronization state and ensure safe reproducible archiving.

To verify delta-spec synchronization before archiving an OpenSpec change, the skill assesses the synchronization state of delta-specs where present and prompts you to optionally sync them before moving the change into the archive path.

You should not archive a change if its tasks are not yet completed, because the skill performs task status verification and artifact completeness checks to ensure only fully completed changes are moved into the archive path.

When an OpenSpec change is archived, the metadata is preserved as the change directory is moved into openspec/changes/archive/YYYY-MM-DD-<name>, maintaining context for future reference while keeping the active changes directory clean.