openspec-archive-change

To archive completed experimental changes, you can use a workflow that verifies artifact and task completion status before moving the change to a designated archive directory. This ensures your project history stays clean and organized.

The best way to synchronize delta specifications with main specifications is to assess the delta files first and optionally sync them with the main specifications before moving the change to the archive directory.

You need to archive a change in an experimental workflow after implementing a new feature and testing it. This formally archives the change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Yes, you need the openspec CLI to verify artifact and task completion status. The CLI is required for performing status checks and managing the archival of experimental changes.

No, you cannot archive a specification if artifact and task completion checks are not passing. The workflow verifies completion status before allowing the change to move to the archive directory.

Synchronizing delta specifications matters before archiving experimental changes because it ensures the main specifications are fully up-to-date with the completed work, maintaining accurate project documentation and history.