openspec-bulk-archive-change

To batch archive multiple completed openspec changes, you select the desired changes via a multi-select prompt and confirm the batch operation. The Skill moves them into a dated archive folder in a single operation after validating artifacts and tasks.

When overlapping capability conflicts are detected during spec changes archiving, the tool checks the codebase implementation evidence to determine the correct order for spec syncing. This conflict-aware resolution prevents accidental overwrites of valid specifications.

Yes, you need openspec CLI access to run the bulk archive operation. The Skill relies on the CLI to validate delta specs, check task completion, and execute conflict-aware spec syncing based on codebase evidence.

Batch spec validation for parallel changes works by collecting artifact status, task completion, and delta spec requirements for each selected change. It then displays a consolidated status table showing success or partial-success before archiving.

Spec sync conflicts are resolved automatically by verifying implementation evidence in the codebase. The tool detects when multiple selected changes touch the same capability and determines the correct ordered syncing sequence to prevent conflicts.

The best way to archive completed spec changes without losing track is to use conflict-aware batch validation. This approach verifies artifacts, tasks, and delta specs while checking the codebase to ensure only implemented updates are synced.