Orchestrate parallel tasks using the subtask CLI. Use when the user wants to run multiple tasks in parallel, delegate work to Codex or other AI workers, manage concurrent operations in isolated git workspaces, or coordinate complex multi-part work.
Orchestrates parallel tasks using isolated git workspaces for concurrent AI worker delegation.
/plugin marketplace add zippoxer/subtask/plugin install zippoxer-subtask@zippoxer/subtaskThis skill is limited to using the following tools:
Subtask lets you dispatch work to parallel workers (like Codex) in isolated git workspaces, with context preservation and progress tracking.
| Command | Description |
|---|---|
subtask run <task> --base-branch <branch> --title "..." "prompt" | Create and execute a task |
subtask list | View all tasks and their status |
subtask show <task> | View task details and conversation |
subtask resume <task> "instructions" | Send follow-up to a paused task |
subtask close <task> | Mark complete and free workspace |
subtask dir <task> | Get workspace path for git operations |
| Status | Meaning |
|---|---|
pending | Created via draft, never executed |
running | Worker currently executing |
paused | Worker finished, awaiting your follow-up |
error | Execution failed |
closed | Done, workspace freed |
Start multiple independent tasks - run them as background commands:
# Task 1
subtask run fix/auth-bug --base-branch main --title "Fix auth token refresh" \
"Fix the token refresh bug in auth/refresh.go - tokens expire but aren't renewed"
# Task 2 (in parallel)
subtask run feat/add-metrics --base-branch main --title "Add request metrics" \
"Add Prometheus metrics for HTTP request latency and error rates"
subtask list
Shows all tasks with status, last activity, and workspace assignments.
When a task is paused (worker finished), review and send follow-ups:
# Check what was done
subtask show fix/auth-bug
# Send more instructions
subtask resume fix/auth-bug "Also add a test for the edge case when refresh token is expired"
When satisfied with the work:
# Check the changes
cd $(subtask dir fix/auth-bug) && git diff
# Commit and push
cd $(subtask dir fix/auth-bug) && git add -A && git commit -m "Fix auth token refresh" && git push
# Free the workspace
subtask close fix/auth-bug
Chain related work with preserved conversation context:
subtask run feat/auth-tests --base-branch fix/auth-bug --context fix/auth-bug \
--title "Add auth tests" "Now add comprehensive tests for the auth module you just fixed"
For read-only questions that don't need a branch:
subtask run ask/how-auth-works --base-branch main --title "How does auth work?" \
--ask "Explain how the authentication flow works in this codebase"
The workspace is freed immediately after the response.
fix/auth-bug not task1subtask list shows progressNo available workspaces:
subtask list # See what's using workspaces
subtask close <task> # Free a completed task
Task in error state:
subtask show <task> # See what happened
subtask run <task> # Retry (auto-recovers if prompt wasn't delivered)
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.