dispatch-middle

What problem does it solve?

Centralized beads often fight the RED→GREEN middle by bloating context and forcing inline changes. Dispatch-middle splits the middle into independent subagents, each running in its own isolated worktree, so the central orchestrator can dispatch once and never write intermediary state.

Core Features & Use Cases

• Independent subagents: each middle participant runs in its own worktree with isolated context.
• Content-bridge relays artifacts: red test content flows between test-author and implementer without shared disks.
• Lean central: central delegates the middle execution entirely to subagents and only collects results.
• Use case: non-trivial bead middles where verification and cross-agent collaboration are required.

Quick Start

Invoke /dispatch-middle <bead> to route the RED→GREEN middle through independent subagents.