openspec-archive-change

To archive OpenSpec changes, validate artifact completion via openspec status, inspect task files for incomplete items, and move the directory to openspec/changes/archive with a date prefix. The process requires user confirmation to prevent accidental archival of unfinished work.

Syncing delta specs involves comparing delta specs against main specs to summarize proposed changes. The archival process offers an option to sync these spec differences before moving the change directory to a dated archive location for safe retirement.

Yes, when no change name is provided, the archival process prompts you to interactively select an active change. It uses openspec list and openspec status JSON output to validate artifacts and tasks before proceeding with the archive operation.

To prevent accidental archival, the process checks artifact completion via openspec status and inspects task files for incomplete items. It requires explicit user confirmation before moving any change directory into the dated archive location.

Yes, the OpenSpec archival process preserves the .openspec.yaml file when moving the change directory. It creates a date-prefixed archive folder and includes checks to avoid name collisions during the repository file operations.

Openspec CLI access is required to run openspec list and status commands for JSON output, which validates artifact completion and task states. This JSON data drives the validation checks needed before performing repository file operations to move changes into the archive.