openspec-archive-change

Archiving a completed change in OpenSpec involves selecting the finalized change and following CLI prompts. The process verifies artifact completion via status JSON and stores it in a date-based archive folder.

Delta specs represent incremental changes against main specs. You sync delta specs before archiving when present, ensuring main specifications are updated and providing a clear summary for traceability.

Yes, the openspec CLI is required to archive workflow changes. It uses status JSON to verify artifacts and tasks are checked, and prompts user input for selecting which completed change to archive.

OpenSpec verifies artifact completion by checking status JSON data before archiving. If artifacts are incomplete or tasks remain, the workflow prompts for user decisions to resolve the incomplete state.

When archiving an OpenSpec change, the workflow preserves relevant metadata and prompts to ensure reproducibility and traceability. This retained context enables future audits of finalized work.