openspec-archive-change

To archive completed OpenSpec changes, ensure all artifacts are finished and delta-specs are aligned, then run the openspec archive command. This finalizes the workflow and generates a concise archival summary for auditing purposes.

Finalizing an OpenSpec change involves validating that artifact status is complete and delta-specs are synchronized with main specs. The archive process then securely stores the record, providing a traceable audit trail of the completed work.

Yes, the openspec CLI is required to archive completed changes. You also need appropriate permissions to execute the archival process, which validates artifact status and delta-spec synchronization before finalizing the work.

If delta-spec synchronization validation fails, the OpenSpec change cannot be archived until alignment with main specs is corrected. The process checks this prerequisite before proceeding to generate an archival summary.

No, when a specific change is not provided, the archive process includes guardrails to prompt for selection. This ensures the correct completed change is targeted before validating its artifact status and synchronizing delta-specs.

No, archiving OpenSpec changes reports any warnings without blocking the archive process. This allows you to finalize and securely preserve the traceable record while remaining informed of potential issues.