openspec-archive-change

Archiving completed changes in an openspec workflow requires verifying artifact and task completion, optionally syncing delta specifications with main specifications, and then moving the change directory to an archive location for a clean project history.

Syncing delta specifications involves assessing completed change artifacts and optionally merging those delta specs with main specifications to ensure project documentation reflects the latest updates before archiving the change directory.

No, archiving an openspec change requires checking artifact and task completion status beforehand using the openspec CLI to ensure only fully implemented changes are moved to the archive location.

The best way to manage completed feature specifications is to sync delta specifications with main specifications after implementation, then move the completed change directory to a designated archive location to maintain clear project evolution records.

Yes, the openspec CLI is required to perform status checks and sync operations, verifying that all artifacts and tasks are complete before the change directory is moved to the archive location.

Openspec change archiving verifies task completion first to prevent archiving incomplete changes, ensuring delta specifications are fully validated and synced with main specifications before moving the directory to archive.