openspec-archive-change

To archive a completed Openspec change, select an active change, validate artifact and task completion, optionally sync delta specs, and confirm archiving. The process moves the change directory into a dated archive path while preserving the .openspec.yaml metadata.

Validating artifacts and tasks before archiving an Openspec change involves guiding users through completion checks. The system provides warnings for incomplete artifacts or tasks to ensure traceability and a clean history before finalizing the archive.

Yes, you can optionally synchronize delta specs when archiving an Openspec change. This synchronization happens after artifact and task validation checks are completed, ensuring delta specs are updated before moving the change directory to the archive.

Yes, archiving an Openspec change preserves the .openspec.yaml configuration file. The archiving mechanism enforces guardrails to ensure this important metadata and other configuration files are maintained when moving the change directory into the dated archive path.

The Openspec archive workflow prompts for change selection instead of guessing to enforce strict guardrails. This prevents incorrect archiving actions, ensuring users explicitly confirm the active change name before proceeding with artifact validation and archiving.

If artifacts or tasks are incomplete during the Openspec change archiving process, the system provides warnings. These guardrails alert users to missing validations, preventing premature archiving and ensuring work artifacts are fully completed and traceable.