openspec-archive-change

To archive completed changes in an openspec workflow, you use a change management process that verifies artifact and task completion before moving the change directory to a timestamped archive location.

Syncing delta specifications before archiving involves assessing and optionally merging delta specs against main specifications to ensure your version control history is clean and organized.

Yes, you need the openspec CLI to archive a completed change, as the CLI is required to perform status checks and list changes before the archiving process moves your files.

If artifact and task completion checks fail during change archiving, the process prevents moving the change directory to the archive, ensuring only fully verified development work is finalized.

Yes, you can automate moving completed development work to a timestamped archive directory using change management scripts that verify delta spec synchronization and task completion beforehand.

You should archive a change in your development workflow after implementing a new feature, testing it, and verifying that all associated artifacts and tasks are fully complete.