Coordinate AI workers, route work to suitable models, or make multi-agent collaboration easier to operate. Parallel task orchestration CLI that dispatches work to AI workers (via Claude Code) in isolated git workspaces. Use when the user wants to draft, create, run, or manage...
Coordinate AI workers, route work to suitable models, or make multi-agent collaboration easier to operate.
Who should use itPower users running several agents, model tiers, or delegated tasks in parallel.
Use this as a fit check before reading install commands.
Works withClaude Code
Platform fit comes after the use case, not before it.
Adoption pathSource-verified setup
Setup evidence is available from README.md · Install the Skill. Review the source before installing.
Trust signalREADME + SKILL.md
1 SKILL.md + README + install evidence, 328 stars, and 1d ago repo freshness at last scan.
Overview
What job does it solve?Agent communication
Coordinate AI workers, route work to suitable models, or make multi-agent collaboration easier to operate.
Who should use it?Power users running several agents, model tiers, or delegated tasks in parallel.
agent coordination and model routing for Claude Code users.
Works withClaude Code
Check platform compatibility after confirming the use case fits your workflow.
How can I adopt it?Source-verified setup
Setup evidence is available from README.md · Install the Skill. Review the source before installing.
Can I trust it?README + SKILL.md
1 SKILL.md + README + install evidence, 328 stars, and 1d ago repo freshness at last scan.
What to compare?5 related skills
Use the comparison list below to avoid adopting the first matching repo blindly.
Quick read
Parallel task orchestration CLI that dispatches work to AI workers (via Claude Code) in isolated git workspaces. Use when the user wants to draft, create, run, or manage tasks, delegate tasks to workers/subagents, or mentions subtask or Subtask.
Claude Skill to do your tasks with subagents in Git worktrees
Why we list it
Public because this is a source-backed installable skill-like repo with enough current evidence to qualify for the shortlist.
Current GitHub metadata is available for zippoxer/subtask.
1 SKILL.md file(s) were found in the recursive tree scan.
Trusted install evidence was extracted from 1 source file(s).
Adoption path for subtask
Primary adoption path
Setup evidence extracted from README.md · Install the Skill. Review source before installing.
Claude will install the Subtask skill at `~/.claude/skills`, and ask you whether subagents should run Claude, Codex or OpenCode.
Alternative install paths
Shown only when the repo exposes another valid install entry for a different host or setup path.
subtask install --guide
/plugin marketplace add zippoxer/subtask
/plugin install subtask@subtask
Compare with these skills
These related skills help you compare use case fit, adoption path, source evidence, and repo activity before adopting this repo.
This is a quick evidence check, not a verdict. Use it to decide which repo deserves a closer read.
Compare subtask vs gstack
gstack is a broader suite than subtask if you want one repo to cover more workflow steps.
Pick this if you want a bundled workflow suite instead of one focused skill.
Dimensionsubtaskgstack
Shortlist fitsolid fitstrong fit
Installclearclear
Sourcestrongusable
Scopefocusedsuite
Compare subtask vs Andrej Karpathy Skills
Andrej Karpathy Skills currently has a stronger shortlist fit than subtask.
Pick this if you want the cleaner shortlist match.
DimensionsubtaskAndrej Karpathy Skills
Shortlist fitsolid fitstrong fit
Installclearclear
Sourcestrongstrong
Scopefocusedfocused
Source evidence
Source excerpts used for this adoption decision. Low-confidence cases link back to GitHub instead of forcing a misleading quote.
README excerpt
README.md
Spawning Tasks
You: fix the auth bug and add API metrics with Subtask
Claude:
├─► Skill(Subtask)
├─► Bash(subtask draft fix/auth-bug ...)
├─► Bash(subtask draft feat/api-metrics ...)
└─⏺ Tasks are in progress! I'll get notified when they're done.
Setup
[!NOTE]
Subtask is in early development. Upcoming releases will simplify installation, solve known bugs, and improve Claude's proficiency.
Install the CLI
Install the Skill
Tell Claude Code:
Setup Subtask with `subtask install --guide`.
Claude will install the Subtask skill at ~/.claude/skills, and ask you whether subagents should run Claude, Codex or OpenCode.
subtask install
### Install the Plugin (Optional)
In Claude Code:
/plugin marketplace add zippoxer/subtask
/plugin install subtask@subtask
This reminds Claude to use the Subtask skill when it invokes the CLI.
SKILL.md excerpt
pkg/install/SKILL.md
Subtask
Subtask is a CLI for orchestrating parallel AI workers. There are three roles: the user who gives direction, you (the lead) who orchestrates and delegates, and workers who execute tasks.
Each worker runs in an isolated git worktree. They can't conflict with each other.
The user tells you what they need. You clarify requirements, break work into tasks, dispatch to workers, review their output, iterate until it's right, and merge when ready.
Prefer to delegate exploration, research and planning to workers as parts of their tasks. Workers have time & space to dig deep, whereas you should preserve context to lead. Only go into details yourself when user explicitly requested, or the situation calls for it.
Mindset
1. Understand before delegating — ask questions, clarify requirements. Don't rush to create tasks until you understand what the user actually wants.
2. Own the complexity — stay on top of all tasks. Surface progress and blockers. Don't make the user chase status.
3. Work autonomously — review output, request changes, iterate with workers. Only involve the user for decisions they need to make.
4. Ask before merging — get user sign-off before merging. Don't merge without user approval.
Or if not merging: subtask close fix/bug
**Critical:** Use the Bash tool with `run_in_background: true` for `subtask send`. Tell the user you're waiting and stop. Don't poll or check. You'll be notified when done.
## Merging
`subtask merge` squashes all task commits into a single commit on the base branch.
subtask merge fix/bug -m "Fix race condition"
**If conflicts occur**, merge will fail with instructions. Follow them.
## Planning Workflows
For complex tasks, add a plan stage: `plan → implement → review → ready`
**You plan (`--workflow you-plan`):** You draft PLAN.md in task folder, worker reviews and pokes holes.
**They plan (`--workflow they-plan`):** Worker drafts PLAN.md in task folder, you review and approve or request changes.