openspec-bulk-archive-change

To bulk-archive multiple completed codebase changes, you select the changes to archive and confirm the operation. The Skill performs status checks, prompts for selection, analyzes delta specs for conflicts, and moves changes into a dated folder while preserving configuration.

When archiving parallel changes causes conflicts, the Skill analyzes delta specs and resolves conflicts by examining codebase evidence. This ensures coordinated releases or review cycles are handled safely without overwriting conflicting modifications.

Yes, you need the openspec CLI installed to archive multiple changes. The Skill requires the openspec CLI to perform status checks, analyze delta specs, and execute the batch-archive operation into a dated directory.

Yes, archiving completed changes preserves the original openspec configuration. The Skill moves archived changes under a dated directory to maintain project history while keeping the original configuration completely intact.

The best way to streamline cleanup for coordinated release cycles is batch-archiving completed changes with conflict-aware handling. This workflow inspects delta specs, resolves conflicts by codebase evidence, and provides detailed status reporting for safe project organization.