openspec-archive-change

You can archive completed workflow changes using the openspec CLI by running the archive-change command. This finalizes the change, moves the directory to the archive location, and preserves metadata and version information for traceability.

Archiving an experimental change involves validating artifacts, tasks, and incremental specs using the openspec CLI. Once validated, the change is archived to separate it from the development branch and conversation context, ensuring reproducibility.

Yes, the archiving process requires the openspec CLI to validate artifacts, tasks, and incremental specs before archiving. This ensures that only completed and properly documented changes are finalized and moved to the archive location.

You need to archive a change when an experimental workflow change is completed and implemented. Archiving separates the finalized change from the active development branch and conversation context while retaining its metadata for traceability.

Yes, the openspec CLI is required to archive workflow changes. It handles the incremental synchronization, validation of artifacts and tasks, and the physical archiving of the change directory to maintain versioning and traceability.