openspec-bulk-archive-change

Batch archiving OpenSpec changes involves reading active-change statuses, checking task completion, resolving delta spec conflicts by analyzing the codebase, and moving eligible changes into a dated archive folder. This reduces manual overhead by processing multiple changes in a single operation.

When delta specs conflict during archiving, the system inspects the conflicts and resolves them by analyzing the codebase to verify implementation status. It syncs specs when implemented and preserves the .openspec.yaml file before prompting for selection and confirmation.

No, archiving requires completed tasks and artifacts. The workflow checks artifact status, tasks, and delta specs to ensure only eligible changes are archived. You must resolve incomplete items before proceeding with the batch archive operation.

Use batch-archive functionality to handle multiple parallel changes in a single operation. It validates completion status, inspects delta specs for conflicts, resolves conflicts via codebase analysis, syncs specs, and organizes archived changes by date in openspec/changes/archive/YYYY-MM-DD-<name>.

Yes, the archiving process preserves the .openspec.yaml file and maintains metadata for audit purposes. Archived changes are organized by date in the archive folder, ensuring traceability and audit-friendly change management.

Batch archive failures typically occur when specific changes have incomplete tasks, unresolved artifact statuses, or delta spec conflicts. The system checks each change individually, and only eligible changes with verified completion and resolved conflicts proceed to archiving.