openspec-bulk-archive-change

You can batch-archive multiple OpenSpec changes by validating their statuses and safely moving them into an archive location. This process uses a prompt-based multi-select workflow to choose which completed changes to archive and confirm the batch operation.

Bulk archiving handles conflicts by detecting them across multiple selected changes and providing automated resolution hints. It maintains a step-by-step audit trail throughout the process to ensure the batch archive operation remains safe and transparent.

Yes, you need the OpenSpec CLI to batch archive completed changes. The skill requires the CLI and reads the repository to determine actual implementations, reconciling codebase evidence to ensure only fully implemented changes are archived.

Yes, bulk archiving OpenSpec changes preserves the original change metadata while safely moving completed items. It maintains an audit trail of actions, recording exactly which changes were archived and where they were relocated.

If you attempt to archive an unimplemented OpenSpec change, the bulk archive operation validates its status and reconciles codebase evidence. It ensures only fully implemented changes are archived, preventing incomplete modifications from being moved.

The best way to maintain an audit trail when archiving completed OpenSpec changes is using a batch archive process. It records exactly which changes were archived and where, while providing a clear step-by-step history of conflict detection and resolution actions.