openspec-archive-change

Archiving OpenSpec changes requires verifying that all artifacts and tasks are complete and delta specs are synchronized, then safely relocating the finalized change into a dated archive directory while preserving original configuration and metadata.

The OpenSpec change archival process involves checking artifact completion, ensuring tasks are complete, assessing delta-spec synchronization, and safely relocating the change to a dated archive directory while preserving configuration files and generating an audit-ready summary.

If delta specs are not synced, the archival workflow assesses synchronization status and prompts for user decisions before proceeding, ensuring the change is archived with full context and an audit-ready summary indicating whether specs were synced.

Yes, the OpenSpec archive workflow safely relocates finalized changes to a dated archive directory while preserving the original configuration files and metadata, maintaining organizational context and producing audit-ready summaries.

The best way to generate an audit summary for archived OpenSpec changes is to use a guided archival workflow that produces a concise record including the change name, schema used, archive location, and whether delta specs were synced during the relocation process.

You should not use automated OpenSpec change archival when artifacts are incomplete, tasks remain unfinished, or delta specs require manual synchronization, as the workflow enforces step-by-step checks and prompts for user decisions before safely relocating the change.