openspec-archive-change

To archive a completed change, you select an active change, validate its artifacts and tasks, optionally sync delta specs, and move it to openspec/changes/archive with the current date while preserving the .openspec.yaml file.

Archiving a change moves it from the active changes directory into openspec/changes/archive, renames it with the current date stamp, and preserves the .openspec.yaml configuration file throughout the process.

Yes, the openspec CLI must be available in your environment because the archival process depends on it to validate artifacts, optionally sync delta specs, and move the change to the archive directory.

You can run the archive process on an incomplete change, but it validates artifacts and tasks and will surface warnings for incomplete items in the final summary before moving the change to the archive directory.

Delta specs can be optionally synced during the archiving process, and the final summary will report the sync status alongside the change name, used schema, and archive location for tracking.

Archiving moves completed changes to a date-stamped directory while preserving the .openspec.yaml file, keeping a historical record of artifacts and tasks instead of permanently discarding the change data.