openspec-bulk-archive-change

Batch archiving completed changes involves processing multiple updates simultaneously to resolve spec conflicts and verify codebase implementation. This Skill automates that workflow by integrating with your code repositories to handle delta specs and generate detailed reporting.

Spec conflict resolution detects and automatically addresses discrepancies in delta specs across multiple changes before archiving. This ensures your project specifications remain synchronized and accurate when multiple completed updates are batch-archived together.

Yes, you need the openspec CLI installed to automate batch-archiving of changes. The Skill requires this dependency to integrate with your code repositories, check implementation evidence, and process delta specs during the archiving operation.

Codebase integration scans your repository to verify implementation evidence before archiving completed changes. This ensures that the code accurately reflects the delta specs, preventing the archival of incomplete or unverified project updates.

Yes, you can review a consolidated status table before confirming any batch archive operation. The Skill prompts user confirmation to ensure you can verify the spec sync status and check for skipped changes before finalizing the process.

Archiving multiple changes simultaneously requires resolving spec conflicts and verifying codebase implementation beforehand. Changes lacking implementation evidence or containing unresolved delta spec conflicts will be skipped, and you must review the detailed reporting to address these gaps.