openspec-archive-change

OpenSpec change archival moves completed changes into openspec/changes/archive/YYYY-MM-DD-<name> to preserve traceability. It validates artifact completion via openspec status, checks outstanding tasks, optionally syncs delta specs, and relocates the change folder while preserving the .openspec.yaml configuration file.

Archiving an OpenSpec change with incomplete items triggers validation checks. The Skill runs openspec status to list incomplete artifacts and parses the tasks file to warn about outstanding tasks, ensuring you are notified of unfinished work before the change is moved to the archive directory.

Yes, delta specs can be synchronized before archiving an OpenSpec change. The Skill detects delta specs and optionally syncs them against main specs during the archival process to ensure the specification repository remains consistent and up to date.

You should archive a change in the experimental OpenSpec workflow when implementation is finished and you need to preserve history and governance. Archiving moves the change from the active directory into a date-prefixed archive folder for long-term traceability.

You do not need to provide a change name upfront to start the OpenSpec archival process. If no change name is provided, the Skill prompts you to select an active change from the available list to proceed with validation and archiving.