openspec-archive-change

To archive completed openspec changes, you supply the change name and the tool validates artifact statuses, task completion, and delta-spec synchronization before moving it to openspec/changes/archive with a date-based naming scheme.

If openspec tasks are not completed, the tool checks completion against tasks.md and surfaces incomplete tasks before archiving, prompting for missing inputs and enforcing guardrails to prevent premature archival.

Yes, archiving an openspec change preserves critical metadata like .openspec.yaml during the move to the archive directory, ensuring configuration remains intact throughout the archival process.

Delta-spec synchronization assesses delta specs against main specs during archiving and suggests syncing if delta exists, ensuring spec changes are reconciled before the change is archived.

Yes, you can provide a specific change name to archive, or the tool will prompt you with available changes to select from, coordinating change selection automatically when needed.

Openspec archive validation fails for incomplete artifacts because the tool validates completion status via openspec status and enforces that all artifacts are done before allowing archival to proceed.