skills.rest
tanaka-yui
tanaka-yuiCOMMUNITY
Explore all skills by this author →
GitHub

cmux-team-dispatch-task

Orchestrate parallel Claude Code tasks across isolated git worktrees with cmux workspaces.

4|Updated Mar 30, 2026
Search Tags:#workflow#task-orchestration#parallel-execution#git-worktree#agent-teams#cmux
One-click install
npx skills add https://github.com/tanaka-yui/yui-cc-plugins --skill cmux-team-dispatch-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmux-team-dispatch-task
Source: https://github.com/tanaka-yui/yui-cc-plugins/tree/main/apps/cmux-team-dispatch-task/skills/cmux-team-dispatch-task
Command: npx skills add https://github.com/tanaka-yui/yui-cc-plugins --skill cmux-team-dispatch-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cmux, jq, git, claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Orchestrate parallel execution of multiple tasks across isolated git worktrees using cmux workspaces. Each task runs in its own Claude Code session, while a parent orchestrator monitors all child sessions. It dynamically discovers available agent types from .claude/agents/ and passes the list to child sessions, which select the appropriate agent themselves. Dispatches immediately without parent-side planning, enabling truly parallel brainstorming/planning and execution across 2+ independent tasks. It supports three layout modes—split, workspace, and claude-teams—and includes a robust status-reporting pipeline via .dispatch directories.

Core Features & Use Cases

  • Dynamic discovery of available agents from .claude/agents/ and per-task agent selection by each child session
  • Immediate parallel dispatch without parent-side planning, suitable for 2+ independent tasks
  • Three layout modes: split (panes within current workspace), workspace (separate sidebars/workspaces), and claude-teams (Agent Teams)
  • Per-task git worktrees and Claude Code sessions for isolation and reproducibility
  • File-based status and result reporting via .dispatch, with optional monitoring and automated completion notes
  • Flexible task intake from inline descriptions or plan references, enabling hybrid workflows

Quick Start

Provide a list of tasks and cmux will dispatch them in parallel across separate workspaces.

What problem does it solve?

Orchestrates parallel execution of multiple Claude Code tasks across independent workspaces, enabling fast, concurrent brainstorming, planning, and execution without sequential bottlenecks.

Core Features & Use Cases

  • Discover and leverage available agents dynamically from .claude/agents/ for task-specific guidance
  • Launch multiple tasks in parallel with deterministic isolation (git worktrees) and separate Claude Code sessions
  • Support for split, workspace, and claude-teams layouts to optimize for task count, duration, and notifications
  • Centralized progress tracking via the .dispatch directory and automated completion signaling
  • Handles mixed task inputs (inline descriptions and plan references) with consistent prompt delivery

Quick Start

Provide a list of tasks and cmux will dispatch them in parallel across separate workspaces.

Frequently Asked Questions about cmux-team-dispatch-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel Claude Code tasks in isolated git worktrees?▼

Parallel Claude Code tasks run across isolated git worktrees by using cmux workspaces to dispatch 2+ independent tasks simultaneously, with each task executing in its own dedicated Claude Code session for complete isolation and reproducibility.

What is the best way to orchestrate multiple AI agent tasks at the same time?▼

Orchestrating multiple AI agent tasks simultaneously is handled by dynamically discovering available agents from .claude/agents/ and passing the list to child sessions, which autonomously select the appropriate agent for immediate parallel dispatch without parent-side planning.

How does cmux handle task isolation and status reporting for parallel execution?▼

Cmux handles task isolation and status reporting by assigning each parallel task its own git worktree and Claude Code session, while enforcing a file-based status and result reporting pipeline via .dispatch directories for centralized progress tracking and automated completion signaling.

Do I need git and jq installed to use cmux for task orchestration?▼

Yes, you need git and jq installed, along with cmux and claude, because task orchestration relies on git for worktree isolation and jq for processing dynamic agent discovery and status reporting data structures.

Can I use different workspace layouts for parallel task execution in Claude Code?▼

You can use three workspace layouts for parallel task execution: split for panes within the current workspace, workspace for separate sidebars, and claude-teams for Agent Teams, allowing you to optimize for task count, duration, and notification preferences.

Why should I avoid sequential task execution when planning multiple independent workflows?▼

Avoiding sequential task execution eliminates bottlenecks during brainstorming, planning, and execution, because parallel dispatch across isolated workspaces allows 2+ independent tasks to progress concurrently without waiting for parent-side planning to complete.

Related Skills

Explore More Software Engineering Skills→
jpoutrinjpoutrin
14

parallel-agents

Orchestrates parallel Codex and Gemini agents for PRD-driven software development.

Community
Advanced
otrebuotrebu
4

finish-feature

Merge a feature branch into main with conflict handling and push.

Community
Basic
datamonsterrdatamonsterr

speckit-worktree-list

Aggregate git worktrees and spec artifacts into a status dashboard.

Community
Advanced
insightfloinsightflo
17

cmux-orchestrate

Orchestrate parallel multi-AI teams across independent cmux processes.

Community
Advanced