openspec-archive-change

Archiving completed OpenSpec changes safely requires validating completion status and syncing delta specs to main specs. This process checks artifact and task completeness, then moves the change directory to a standardized dated archive folder to prevent losing unsynced work.

Organizing finished OpenSpec changes is best handled by generating standardized dated archive names and moving the experimental change directories into a central archive folder, which eliminates naming conflicts and creates an organized, auditable history of completed work.

Checking OpenSpec change completeness involves validating artifact status and task lists. The archival process automatically evaluates these components and warns you of incomplete work, providing guardrails against archiving partial changes before all implementation tasks are finished.

Yes, you need to sync delta specs to main specs before archiving an OpenSpec change. The process assesses delta spec sync status, prompts you to sync if needed, and ensures overall specification consistency across the codebase prior to moving the change to the archive.

Archiving incomplete OpenSpec changes leaves missing artifacts and unsynced delta specs, leading to inconsistent codebases. Manual archival lacks guardrails, but automated completion validation prevents partial changes from being stored and flags unfinished tasks before the directory is moved.