openspec-bulk-archive-change

You can archive multiple completed git changes at once by running a batch operation that archives all selected changes simultaneously, resolving spec conflicts by verifying actual codebase implementation before moving them to the archive.

Yes, you can archive parallel changesets in a single operation through a user-driven selection process, allowing you to clean up multiple completed features efficiently while ensuring spec consistency across the archived changes.

Bulk archiving handles spec conflicts intelligently by automatically checking the codebase for actual implementation, verifying that the changes are truly implemented before resolving conflicts and proceeding with the archive operation.

Yes, you need the openspec CLI installed and available in your environment, as it is required for change management and artifact status checks during the batch archiving workflow.

The best way to clean up active changes after parallel development is to use a batch archiving operation that allows you to select multiple completed changes simultaneously, reporting detailed status and ensuring spec consistency.

Archiving changes in bulk instead of one by one streamlines the cleanup process when dealing with parallel development efforts, saving time by resolving spec conflicts and archiving multiple completed features in a single operation.