openspec-archive-change

To archive completed OpenSpec changes safely, validate artifact status and task completion, sync delta specs, then move the change into a dated archive directory to prevent accidental overwrites.

Finalizing specification-driven development workflows requires checking task progress, reviewing delta spec synchronization against main specs, and archiving the change record into dated storage for documentation consistency.

Yes, you need openspec CLI access to manage change archiving because it requires archive path management and guardrails to prevent accidental selection or unsynced finalization.

To sync delta specs before closing a change request, the system detects delta specs, compares them with main specs, and supports syncing them during the completion check phase before archiving.

You cannot cleanly archive an OpenSpec change with incomplete tasks because the completion check reviews artifact status and task progress, warning you about anything unfinished before moving it to the archive.

If you try to overwrite an existing archive directory, the safe archiving guardrails prevent the action by moving the change into a unique dated archive path to avoid breaking the workflow.