openspec-archive-change

After finishing a change implementation, you archive it to keep the workspace organized and prevent rework. The workflow validates completion via openspec status, moves the change directory to openspec/changes/archive with a dated name, and generates a summary.

When archiving a change, the workflow assesses delta-spec synchronization before moving the directory. This check ensures delta-specs are properly aligned and metadata is preserved during the safe archival process.

You should archive a change when implementation is complete and you want to finalize it. Archiving moves the change to stable storage, keeping the workspace organized and allowing later reference for audits or rollback.

Yes, the workflow validates artifact and task completion by checking openspec status. It prompts for change selection when needed and ensures tasks are complete before safely moving the change to the archive directory.

Yes, archived changes can be referenced for audits or rollback. The process moves the change directory into openspec/changes/archive with a dated name and generates a summary while preserving metadata for future access.