openspec-archive

To archive OpenSpec changes after deployment, you can use a Skill that moves completed changes to an archive state and synchronizes specification files. It requires the OpenSpec CLI to list, validate, and archive the changes automatically.

OpenSpec specification synchronization is the process of updating relevant spec files to reflect archived changes. This ensures documentation accuracy post-deployment by keeping deployed changes and their associated specifications aligned.

You update API documentation after deploying an OpenSpec change by archiving the change. This action automatically synchronizes the associated specification files to reflect the newly deployed endpoint or modification.

Yes, you need the OpenSpec CLI to archive changes. The CLI is required to list, validate, and archive changes, ensuring the associated specification files are correctly synchronized during the release lifecycle.

You should archive an OpenSpec change after successfully deploying the associated modification. This manages the change lifecycle by formally moving the completed change to an archive state and updating the documentation.

The best way to manage the OpenSpec change lifecycle is by archiving deployed changes and updating specs. This streamlines the release process by automating the transition to an archive state and synchronizing documentation.