agents/skills/orchestrator

What problem does it solve?

It solves the complexity and fragility of orchestrating multiple isolated “worktree subagents” while keeping bead/task state consistent and ensuring merges and cleanup happen against the correct branches.

Core Features & Use Cases

• Worktree-first delegation: coordinates subagents that do not directly implement changes, keeping implementation isolated and trackable.
• Bead lifecycle control: creates beads, updates status, and closes/commits bead state so tracking remains reliable across parallel work.
• Robust merge + cleanup sequence: enforces correct merge semantics, safety checks, and deterministic removal of temporary branches/worktrees.
• Failure-mode guardrails: includes explicit handling for cwd/worktree re-anchoring and cross-repo dispatch/worktree placement issues.

Quick Start

Ask the orchestrator to delegate implementation to worktree subagents, then merge each worktree-agent branch into the intended version branch and close the associated beads using the prescribed lifecycle steps.