openspec-archive-change

To archive completed changes in OpenSpec, use the openspec CLI to verify task completion, synchronize delta specs with main specs, and move the change to a dated archive directory while preserving metadata.

OpenSpec checks artifact completion status and task completion before archiving to prevent partial deployments. It also analyzes delta specs against main specs to determine if synchronization is needed prior to archival.

During the OpenSpec archival process, the workflow analyzes delta specs against main specs to identify required changes for synchronization, ensuring the archive reflects the complete and final implementation state.

You cannot archive an OpenSpec change if implementation tasks are incomplete. The workflow explicitly checks artifact completion status and task completion to prevent partial deployments from being archived.

The best way to maintain traceability for finished OpenSpec workflows is archiving completed changes into a dated directory. This preserves related metadata, notes, and delta specs sync state for consistent workflow history.

Yes, you need the openspec CLI to archive change management artifacts. The archival process requires CLI access to openspec/status and openspec/changes to safely verify completion and move metadata.