openspec-bulk-archive-change

Batch-archiving OpenSpec changes involves selecting active changes, validating artifact status and tasks, resolving delta spec conflicts, and archiving into a date-stamped directory. This streamlines cleanup by handling multiple completed changes in a single operation.

Spec conflict resolution works by inspecting delta specs against the codebase to determine what is actually implemented. It validates delta spec discovery and intelligently resolves conflicts before archiving changes into the target directory.

Validation checks include per-change artifact status, tasks.md progress verification, and delta specs discovery. These checks ensure each active change has completed artifacts and tasks before archiving into a date-stamped directory.

Yes, the .openspec.yaml file is preserved during archiving. The skill maintains history and directory structure by keeping this configuration file intact when moving completed changes into the date-stamped archive directory.

Yes, you can select specific active changes for batch archiving rather than archiving all changes. The skill supports choosing multiple active changes individually before confirming and executing the archive operation.