pac-openspec-archive-change

Archiving a completed change in openspec involves moving implemented changes to the changes archive directory. The process verifies status, evaluates delta specs, and prompts for user confirmation to ensure all artifacts are preserved with provenance metadata.

When archiving, delta specs are assessed and optionally synchronized before the change is moved. This ensures that any delta spec modifications are considered and properly preserved alongside artifacts during the finalization process.

Yes, archiving workflow changes requires the openspec CLI and access to relevant openspec data stores. The CLI facilitates status checks and delta-spec assessment, applying guardrails that prompt for decisions when artifacts or tasks are incomplete.

Archiving an openspec change with incomplete tasks triggers guardrails that prompt for user decisions before proceeding. This prevents finalizing unfinished artifacts and ensures the archived change maintains provenance and consistent auditable status.

Delta-spec assessment should be used when a change is implemented and ready for the openspec archive. It evaluates specification differences to ensure any delta specs are properly considered and synchronized before finalizing the long-term storage.