parallel-cleanup-feature

Parallel feature cleanup is automated by registering changes in a merge queue, running pre-merge validation, and handling cross-feature rebasing. This workflow coordinates OpenSpec feature branches merged concurrently while preserving resource claim integrity.

Cross-feature rebasing works by fetching the latest main branch and rebasing the feature to resolve conflicts with other parallel changes. This ensures concurrent OpenSpec feature branches integrate smoothly without ordering issues or broken pipelines.

A coordinator service is required to expose merge-queue, feature-registry, and lock capabilities via HTTP or MCP tools. If unavailable, the workflow seamlessly falls back to linear cleanup to complete the feature integration.

After a parallel feature merge completes, the resource claim lifecycle deregisters the feature to free claims for dependent features. This prevents stale feature registrations and avoids integration delays for subsequent concurrent merges.

The workflow applies to OpenSpec feature branches that must be merged concurrently. It relies on OpenSpec feature registrations and a coordinator service exposing merge-queue and feature-registry capabilities to manage the parallel cleanup process.

Concurrent feature merges cause broken pipelines due to resource conflicts, ordering issues, and stale feature registrations. Prevent this by using a merge queue coordinator to run pre-merge checks and enforce ordered merging across parallel branches.