openspec-archive-change

To archive completed openspec changes, you provide the change name and the workflow validates artifact completion via openspec status, checks tasks.md, and moves the directory to openspec/changes/archive with date-stamped naming to preserve the audit trail.

During change archival, openspec status warnings do not block the process; the workflow proceeds with archiving the completed change and includes any existing warnings in the final archival summary for review.

Yes, before archiving an openspec change, the workflow assesses delta spec synchronization and optionally syncs your delta specs with main specs to ensure consistency before moving the change directory to the archive.

Archived openspec change directories are named using the current date and the change name, created under openspec/changes/archive, and the original directory is moved while preserving its .openspec.yaml configuration file.

To check task completion before archiving, the workflow inspects tasks.md within the change directory, counting completed versus incomplete tasks to ensure all implementation work is finished prior to archival.

You can start the openspec archive workflow without specifying a change name, but the workflow enforces a guarded flow by prompting you to select the specific completed change you want to archive.