openspec-archive-change

To archive completed changes in an OpenSpec workflow, you run the archival process to validate artifact and task completion, assess delta-spec sync, and move the change directory into a timestamped archive. This preserves the auditable history of your finalized feature changes.

If you attempt to archive an OpenSpec change with incomplete tasks, the process validates statuses via openspec status and tasks.md to prevent unsafe archival. It enforces completion checks to ensure no unfinished artifacts or tasks are moved to the archive directory.

You do not strictly need to specify the change name upfront when archiving OpenSpec artifacts. If the change name is missing, the workflow interactively prompts you to provide it before proceeding with artifact validation and delta-spec sync assessment.

You should use OpenSpec archival for release readiness when finalizing feature changes and preparing for deployment. It ensures all artifacts, tasks, and delta specifications are synced and safely preserved in a timestamped archive directory for audit purposes.

Archiving an OpenSpec change does not delete essential configuration files. The safe archival process specifically preserves the .openspec.yaml configuration file while moving completed artifacts and task records into the timestamped archive directory.