openspec-archive-change

You can archive completed changes by selecting a specific change name or relying on auto-detection from context, ensuring all artifacts and tasks are complete and delta spec sync state is verified before finalizing the archive.

Before archiving a specification change, the system checks that all associated artifacts and tasks are fully complete and verifies the delta spec sync state to ensure specifications are properly synchronized before finalizing.

Yes, finalizing and archiving changes requires the openspec CLI and access to the experimental workflow directory to execute the archiving process and verify delta spec sync state.

You can either explicitly specify a change name to archive or allow the system to auto-detect the completed change from the current context within the experimental workflow environment.

The archiving process enforces artifact and task completion checks, preventing the finalization of incomplete changes and ensuring only fully implemented specifications are stored in the archive.

Yes, the archiving process provides a summary of the archiving operation and results, confirming that the completed change has been finalized, documented, and stored for future reference.