openspec-archive-change

Archiving a completed change involves verifying artifact and task completion before moving the change to a designated archive location. This process ensures a clean and organized project history within the experimental workflow.

Syncing delta specifications with main specifications involves reconciling the experimental changes captured in delta specs with the primary project specifications. This synchronization step must occur before archiving to ensure the main specifications remain accurate and up to date.

Yes, you need the openspec CLI to perform status checks and archiving operations. The CLI is required to verify that all artifacts and tasks associated with the experimental change are fully completed before the archive process can execute.

You should archive changes in an experimental workflow after implementing a new feature, testing it, and confirming all associated tasks and artifacts are complete. Archiving marks the change as organized and finalized, preventing clutter in your active workspace.

No, you cannot archive an experimental change if task completion verification fails. The archiving process explicitly checks artifact and task completion status beforehand, blocking the operation to prevent archiving incomplete or broken changes.