openspec-archive-change

To archive experimental changes, validate artifact completion, assess delta-spec sync status, and relocate the change to a dated archive directory. You can provide the change name directly or let the tool prompt you to select an active change for finalization.

If artifacts or tasks are incomplete during change archival, the tool prompts for manual confirmation. It supports optional syncing of artifact status data before proceeding with the archival relocation to ensure traceability.

Yes, archiving experimental changes requires the openspec CLI and access to artifact status data. These dependencies drive optional syncing and archival actions to finalize and store completed workflow artifacts.

Delta-spec sync status is assessed during change archival to determine if optional syncing is needed before relocation. This stepwise validation ensures completed artifacts are properly synchronized before moving to the dated archive directory.

Yes, the .openspec.yaml file travels with the archived change to maintain traceability. This ensures the configuration data remains accessible alongside the stored artifacts in the dated archive directory.

The best way to finalize artifacts is through stepwise validation of completion, delta-spec sync assessment, and archival relocation. This process locks in the change and stores it in a dated directory for future reference and traceability.