openspec-archive-change-ai-kit

Archiving a completed OpenSpec change requires validating artifacts via openspec status and tasks.md, optionally syncing delta specs under openspec/changes/<name>/specs/, then moving the directory into a timestamped archive location.

When archiving an OpenSpec change with incomplete tasks or artifacts, the process detects incomplete items via openspec status and tasks.md, warns the user, and requires explicit confirmation before proceeding with the archival move.

Yes, openspec CLI support is required to archive changes, because the process executes openspec list and openspec status commands to validate artifact completion and check task status before moving the directory.

During OpenSpec workflow finalization, delta specs under openspec/changes/<name>/specs/ are detected and compared against main specs to summarize differences, then optionally synced via an openspec-sync-specs approach before archiving.

You should not archive an OpenSpec change directory when artifact validation via openspec status or task completion checks in tasks.md reveal incomplete deliverables, as the workflow is designed to prevent accidental archival of unfinished work.