taskmaestro

Orchestrating parallel Claude Code tasks in tmux involves distributing multiple instances across separate panes with isolated git worktrees, enabling concurrent development without context switching. The Skill manages task assignment, monitors status, and consolidates pane-specific workflow control.

Git worktree isolation assigns a separate working directory to each tmux pane, ensuring deterministic task execution for Claude Code. This prevents file conflicts when multiple parallel instances modify code simultaneously during coordinated workflow orchestration.

Tmux is required as the environment to orchestrate multiple Claude Code sessions across panes. The Skill manages pane-specific workflows, preflight checks, and RESULT.json signaling within a single tmux session to coordinate parallel development tasks.

You assign tasks to specific tmux panes using the assign subcommand. This directs individual Claude Code instances to execute isolated worktree tasks while the orchestrator monitors execution status and collects RESULT.json output signals from each worker.

Optional review automation is supported after parallel tasks finish. The orchestration workflow triggers review checks once per-pane task execution completes and RESULT.json signals are collected from the tmux worker panes, streamlining collaborative code validation.

Running multiple Claude Code instances in tmux requires careful resource management, as each isolated worktree pane consumes compute independently. Preflight checks validate environment readiness, but complex dependencies between parallel tasks may still create coordination bottlenecks during execution.