openspec-archive-change

To archive completed OpenSpec changes, the Skill moves the finalized change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving the .openspec.yaml metadata and generating a clear operation summary.

Before archiving an OpenSpec change, the Skill runs openspec status to validate artifact completion, checks for remaining tasks, and reports any warnings without blocking the final archiving process.

Delta spec synchronization during archiving analyzes delta specs against main specs to determine if synchronization is needed, and can trigger the sync process automatically if requested by the user.

You need to archive a change in the OpenSpec workflow after implementation is fully complete, ensuring all artifacts are finalized, tasks are checked, and the change is ready for audit-ready preservation.

Yes, archiving an OpenSpec change preserves the .openspec.yaml file along with all important metadata, moving everything to a date-stamped archive path for future reference and audit readiness.

Yes, you can archive an OpenSpec change with remaining warnings because the Skill reports any status warnings without blocking the archive, ensuring changes can be finalized even with non-critical issues.