openspec-archive-change

To archive completed OpenSpec changes, the Skill moves the change directory into a date-prefixed archive folder. This workflow preserves metadata, delta specs, and associated artifacts for long-term traceability and replay.

Yes, you need the OpenSpec CLI installed to perform archival operations. The Skill leverages the CLI to move finished change directories to an archive folder with a date-based name while enforcing validation checks.

Before archiving OpenSpec changes, the Skill enforces validation checks to verify artifact and task completion. If items are incomplete, it prompts you for confirmation to proceed with archiving or halt the operation.

Yes, the Skill detects and summarizes delta specs versus main specs. It prompts you to decide whether to sync changes into the main specs or archive the directory without syncing.

A date-prefixed archive folder ensures safe, auditable organization of archived OpenSpec changes. This naming convention preserves metadata and configurations, making finished feature changes easy to locate for future reference.

The best way to manage versioning for experimental OpenSpec changes is using a validation and archival workflow. This process verifies task completion, assesses delta specs, and securely archives directories to maintain traceability.