openspec-archive-change

Yes, the process generates a dated archive path to preserve essential metadata for auditability. This ensures that completed changes are systematically organized and traceable within the archived directory.

To archive completed changes, the system checks artifact completion, task status, and delta-spec synchronization before moving the change to a dated archive directory. You can provide a specific change name or let the system prompt you to select an active one.

If delta-specs are not synced, the system evaluates the synchronization state and provides guided prompts for optional syncing before proceeding with the archive. The final summary will include warnings about any incomplete artifacts or tasks.

Yes, the archival process automates task completion and artifact status checks. It evaluates these guardrails automatically and outputs a concise summary detailing the archive location, sync state, and any warnings for incomplete items.

You need to archive a completed change to preserve project history, ensure traceability, and avoid rework caused by incomplete states. It safely moves finished changes to an archived directory after verifying all required artifacts are complete.

Yes, the process generates a dated archive path to preserve essential metadata for auditability. This ensures that completed changes are systematically organized and traceable within the archived directory.