openspec-archive-change

To archive completed OpenSpec changes, the skill validates artifact and task statuses via openspec status, optionally synchronizes delta-specs, and moves files to openspec/changes/archive with date-based naming while preserving .openspec.yaml metadata.

You should archive an OpenSpec change when its implementation is complete and verified, ensuring artifact and task status checks pass to prevent regressions and finalize the historical record.

Yes, you can optionally compare and synchronize delta specs before archiving, ensuring main specs remain up to date before the change is moved to the archive directory.

The OpenSpec archive process moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name>, applying date-based naming conventions while preserving the original .openspec.yaml metadata file.

If artifact or task status checks fail during archiving, the process requires you to verify completion via openspec status before proceeding, ensuring only fully implemented and verified changes are archived to prevent regressions.

You can provide a change name directly or leave it blank to be prompted automatically, allowing the skill to handle change selection interactively before performing artifact checks and archival file operations.