openspec-archive-change

To archive completed OpenSpec changes, the process validates artifact and task completion, checks delta spec sync state, generates a date-based archive path, and moves the finished work to prevent overwrites and preserve a verifiable audit record.

Archiving an OpenSpec change with incomplete tasks is blocked by the artifact and task completion checks. The process assesses delta spec sync state and prompts for change selection, ensuring only fully finalized and validated deltas are moved into the archive directory.

You need to archive a delta spec in OpenSpec when finalizing a change, locking in implementation decisions, and preserving the work for audit, reuse, or rollback. This ensures compliance by retaining artifact and delta spec information safely.

You cannot overwrite an existing archive directory when archiving OpenSpec changes. The process handles naming and ensures no overwrite occurs, automatically generating a unique date-based archive path to safely retain your artifact and delta spec information.

Yes, OpenSpec change management enforces prompts for change selection if a specific change is not provided. This ensures the correct delta is targeted before validating artifact completion and creating the archive directory for the historical record.

The best way to lock in implementation decisions after completing a feature is to archive the change in OpenSpec. This moves finished work into an archive, validating artifact completion and preserving a verifiable historical record for audit or rollback.