openspec-coordinator-worktree

To convert OpenSpec proposals into parallel git worktrees, you parse the proposal to create linked epic and task issues in a coordinator tracker, then generate isolated feature branches and worktrees per task for concurrent agent execution.

Orchestrating multi-agent implementation with git worktrees involves creating separate branches per task, generating execution scripts for parallel or swarm strategies, launching agents in isolated worktrees, and merging completed branches into a central feature branch.

Yes, spec-driven feature development requires a coordinator or Beads-like issue service to track tasks and link dependencies, alongside Git with worktree support to manage the isolated branches and merge results.

Yes, you can run sequential, parallel, or swarm execution strategies by generating specific execution and monitoring scripts that launch agents, update task statuses, and visualize progress across the isolated git worktrees.

Merging completed task branches involves integrating individual worktree branches back into a central feature branch, running validations, archiving the original OpenSpec proposal, and closing the epic with audit metadata.

You should avoid isolated git worktrees if you lack OpenSpec-formatted proposals, a coordinator issue service, or Git worktree support, as these are required to create branches, orchestrate execution, and merge results reliably.