A Claude Code skill that turns your session into a command center. Stop juggling terminals — dispatch work to background AI agents and stay in flow.
/dispatch plans tasks as checklists, fans out to background workers — Claude, GPT, Gemini — and tracks progress. You stay in one clean session. Workers do the heavy lifting in isolated contexts.
/dispatch use sonnet to find better design patterns for the auth module
The dispatcher never does the actual work. It plans, delegates, and tracks. The heavy reasoning — code review, refactoring, test writing — happens in isolated worker contexts. Your main session's context window is preserved for orchestration, not consumed by implementation details.
This is the part most agent orchestrators get wrong. When a /dispatch worker gets stuck, it doesn't silently fail or hallucinate. It asks a clarifying question — the dispatcher surfaces it to you, you answer, and the worker continues without losing context. No restart, no re-explaining, no lost work.
Worker is asking: "requirements.txt doesn't exist. What feature should I implement?"
> Add a /health endpoint that returns JSON with uptime and version.
Answer sent. Worker is continuing.
The moment a worker is dispatched, your session is immediately free. Dispatch another task. Ask a question. Write code. The dispatcher handles multiple workers in parallel, reports results as they arrive, and surfaces questions only when they need your input. No polling, no tab-switching, no "is it done yet?"
Mix models per task. Claude for deep reasoning, GPT for broad generation, Gemini for speed. Reference any model by name — if it's not in your config, /dispatch auto-discovers and adds it.
/dispatch use opus to review this PR for edge cases
/dispatch use gemini to refactor the config parser — it's getting unwieldy
Requires Claude Code as your host session. Dispatch is a skill that runs inside Claude Code — the host plans tasks and spawns workers. Other CLIs like Cursor and Codex work as workers only (background agents that execute subtasks).
npx skills add bassimeledath/dispatch -g # user-level (all projects)
npx skills add bassimeledath/dispatch # project-level (team-shared)- You run
/dispatch task description - A checklist plan is created at
.dispatch/tasks/<id>/plan.md - A background worker picks it up and checks off items as it goes
- If the worker has a question, it asks — you answer — it continues
- You get results when it's done, or ask for status anytime
On first run, /dispatch auto-detects your CLIs (claude, agent, codex), discovers available models, and generates ~/.dispatch/config.yaml. No manual config needed.
Three sections in ~/.dispatch/config.yaml:
Backends — CLI commands for each provider:
backends:
claude:
command: >
env -u CLAUDE_CODE_ENTRYPOINT -u CLAUDECODE
claude -p --dangerously-skip-permissions
cursor:
command: >
agent -p --force --workspace "$(pwd)"
codex:
command: >
codex exec --full-auto -C "$(pwd)"Models — one line each, mapped to a backend:
models:
opus: { backend: claude }
sonnet: { backend: claude }
gpt-5.3-codex: { backend: codex }
gemini-3.1-pro: { backend: cursor }Aliases — named shortcuts with optional role prompts:
aliases:
security-reviewer:
model: opus
prompt: >
You are a security-focused reviewer. Prioritize OWASP Top 10.Host (required):
- Claude Code (
claude)
Workers (optional — for multi-model dispatch):
- Cursor CLI (
agent) - Codex CLI (
codex) - Any CLI that accepts a prompt argument
Skills CLI (recommended):
npx skills updateThis updates all installed skills to their latest versions. Run npx skills check first to see what's changed.
Symlinked to a local clone? If your .claude/skills/dispatch is a symlink to a local git checkout, just pull:
cd /path/to/your/dispatch && git pullChanges are picked up immediately — Claude Code hot-reloads skills from disk.
MIT