openspec-archive-change

To archive completed changes in a specification management workflow, you can automate the process to ensure artifacts and tasks are complete before storing them. This preserves all relevant change information with a summary.

Finalizing and storing completed workflow changes involves verifying artifact completion, assessing delta spec sync state, and archiving the changes with a generated summary of the process and outcomes.

Yes, archiving experimental workflow changes requires the openspec CLI and the openspec-sync-specs skill to assess delta spec sync state and properly archive the completed change documentation.

Archiving requires assessing the sync state of delta specs before proceeding. The archival process checks the completion status of artifacts and tasks to ensure changes are properly documented and stored.

Change management archival requires status verification to ensure that all artifacts and tasks are fully complete before archiving. This prevents the loss of incomplete information and provides an accurate summary of outcomes.

The best way to automate change archival in openspec is using a dedicated archival skill that checks completion status, assesses delta spec sync state, and generates an archive summary for completed changes.