openspec-archive-change

You can archive completed change management artifacts by running a CLI workflow that verifies artifact and task completion, optionally synchronizes delta specs, and stores the output under an archive directory. This preserves existing metadata during the archival process.

Archiving changes in openspec involves selecting a completed change, verifying that all artifacts and tasks are complete, and moving it to a date-based target folder under the archive directory. The process applies guardrails to prompt for confirmation when delta specs require synchronization.

Yes, the archival workflow requires artifact and task completion checks before proceeding. If artifacts, tasks, or delta specs require attention, the system applies guardrails and prompts the user for confirmation to prevent archiving incomplete changes.

Yes, the archival process preserves existing metadata when it creates the archive entry under the date-based target directory. This ensures project history remains clean and auditable without losing any contextual information from the original change.

When delta specs require attention during change archival, the workflow applies guardrails and prompts for user confirmation. It offers optional delta spec synchronization to ensure the archived change reflects the latest specification status before completing the process.

The workflow prompts for confirmation to apply guardrails against accidental or premature archival. It checks whether artifacts, tasks, or delta specs require attention, ensuring only fully implemented and verified changes are archived in the project history.