openspec-archive-change

To safely archive completed openspec changes, you can run pre-archive validation checks on task checklists and artifact completion status to prevent accidental archival of unfinished work and ensure changes are moved to a date-prefixed directory only when fully complete.

When archiving an openspec change, the workflow evaluates unapplied delta specs and prompts you to sync changes to main specifications before archiving, maintaining specification consistency and preventing delta spec data loss.

Yes, you need to sync delta specs to main specs before archiving openspec changes to maintain specification consistency, as the pre-archive validation assesses the delta spec sync state and warns you about unapplied changes.

Pre-archive validation in openspec change management works by verifying artifact completion status, checking task checklists, and assessing delta spec sync state to warn users of incomplete work before moving change directories to the archive location.

You can prevent accidental archival of incomplete work in the openspec experimental workflow by applying mandatory pre-archive validation checks that verify artifact completion and task checklist status before allowing any change directory to be archived.

The best way to finalize and archive openspec feature changes is to use a validation workflow that checks artifact completion, task checklists, and delta spec sync state, moving verified changes to a date-prefixed archive location to keep the changes directory organized.