openspec-archive-change

To archive openspec changes, the workflow validates artifact and task completion via openspec status, optionally syncs delta specs, and safely moves the change to a dated archive path. This preserves metadata while keeping active workflows clean and auditable.

Delta-spec syncing checks for pending specification differences before archiving and offers to integrate them. This ensures the archived change reflects the final implemented state, maintaining accurate traceability between the active workflow and the preserved history.

You should archive a change in an openspec workflow when implementation is complete and all artifacts and tasks are validated. Archiving preserves the auditable history of completed work and removes finished items from the active workspace to maintain cleanliness.

No, archiving requires successful artifact and task validation via openspec status. The workflow enforces these safety checks to ensure only fully implemented changes are moved to the archive directory, preventing incomplete work from being preserved as historical records.

Completed openspec changes are moved into a dated folder structure at openspec/changes/archive/YYYY-MM-DD-<name>. This dated path organization ensures chronological traceability and preserves metadata for auditable workflow history.

Yes, the archive process safely moves the change while preserving all relevant metadata. This ensures the auditable history remains accurate and complete, allowing past changes to be reviewed with their original context intact within the archive directory.