openspec-archive-change

To archive an openspec change, the workflow verifies artifact completion via openspec status, checks tasks.md for incomplete items, and moves the change directory to a dated archive location while preserving .openspec.yaml. Users must confirm any incomplete items before the directory is moved.

When archiving openspec changes with incomplete tasks, the workflow inspects tasks.md, warns you about pending items, and requests explicit confirmation before proceeding to the dated archive directory. This prevents accidentally finalizing unfinished work or losing track of remaining artifacts.

Delta spec synchronization compares delta specs to main specs, summarizes required updates, and offers options to sync before archiving. The workflow can invoke a sync process via a task invocation to ensure your main specifications reflect the completed change.

Yes, archiving completed openspec changes requires the openspec CLI for listing active changes and running status checks. The CLI provides the necessary status verification and artifact completion data before the workflow moves the change directory to the archive.

To prevent accidental archiving, the workflow uses interactive selection to prompt you to choose an active change when a specific name is not provided. It also checks for name conflicts in the dated archive directory before moving any files.

The best way to finalize an experimental openspec change is to run completion checks, optionally sync delta specs to main specs, and move the change directory to openspec/changes/archive with an audit-friendly dated name while preserving the .openspec.yaml configuration.