openspec-archive-change

To archive experimental changes in an openspec workflow, use the archive-change command followed by the change name. This finalizes completed implementations and marks them as done within the version control system.

Yes, you can optionally sync delta specifications with main specifications before archiving an openspec change. This ensures all modified specs are synchronized before the experimental change is marked as fully completed.

Yes, archiving an openspec change includes completion verification. The process checks the completion status of all associated artifacts and tasks to ensure everything is finished before finalizing the workflow.

Yes, you need the openspec CLI tool to manage change tracking and archiving. The Skill requires this dependency to automate the archival of experimental changes within the openspec architecture.

The best way to finalize experimental changes in version control is using a structured workflow management tool like openspec. It automates completion checks and archives changes to maintain a clean project history.

You should not use automated archive change if your experimental changes are incomplete. The process checks for the completion of all associated tasks and artifacts, blocking finalization if required workflow elements are missing.