openspec-archive-change

To archive completed OpenSpec changes, validate artifact and task status via OpenSpec commands, optionally sync delta specs to main specs, and move the change into a date-stamped archive directory to preserve metadata.

You should archive a change in OpenSpec when finalizing it after implementation to preserve artifacts, maintain traceability, and ensure all specs are tracked before moving the folder into the archive directory.

Yes, archiving changes requires an active OpenSpec CLI because the workflow relies on its commands to check artifact completeness, verify task status, and synchronize delta specs before moving files.

When archiving an OpenSpec change, the workflow compares delta specs to main specs and optionally synchronizes them before moving the completed change into the archive directory with its metadata preserved.

OpenSpec warns you when archiving a change with incomplete artifacts because the workflow validates completeness and task status to ensure traceability, prompting for confirmation before proceeding with the archive process.

Yes, moving changes to the OpenSpec archive preserves metadata by placing the completed change into a date-stamped folder within the archive directory, ensuring state and traceability are maintained.