openspec-bulk-archive-change

Batch-archiving OpenSpec changes consolidates completed changes safely by moving them to openspec/changes/archive with dated folders, detecting conflicts via delta specs, and validating task completion to keep histories organized.

Conflict detection works by comparing delta specs and scanning the codebase for implementation evidence before archiving, ensuring completed artifacts and tasks are validated and conflicts are resolved before moving changes to dated archive folders.

You cannot archive OpenSpec changes before task completion because the skill validates artifact and task completion and requires explicit user confirmation after resolving conflicts before moving changes to the archive.

Batch-archived OpenSpec changes are moved to openspec/changes/archive with the current date, preserving history and consistency while providing per-change outcome reports to track archival results.

Explicit confirmation is required for batch-archiving OpenSpec changes because the operation validates artifact completion, resolves conflicts via delta specs, and moves multiple changes to dated archive folders, requiring user approval before finalizing.