openspec-archive-change

To archive completed OpenSpec changes safely, the workflow validates artifact completion and task status using openspec status --json, optionally syncs delta specs, then moves the change to a dated archive path while preserving .openspec.yaml metadata.

You cannot archive an OpenSpec change before task completion because the process enforces artifact and task status validation via openspec status --json to prevent premature archiving and ensure workflow integrity.

When moving a change to the archive folder, the .openspec.yaml metadata file is explicitly preserved during the file move operation, ensuring historical context and configuration remain intact in the dated archive path.

You need to sync delta specs during change archiving when synchronization assessment detects pending updates, allowing optional syncing prior to the move to ensure delta spec alignment before the change is archived.

OpenSpec change archiving works without a specified change name by using prompt-driven change selection, interactively asking the user to select the target change before proceeding with validation and archiving.

The best way to keep OpenSpec workflows clean after implementation is archiving completed changes, which validates artifacts and delta specs, then relocates the change to a dated path with preserved metadata and a summary of actions performed.