Zippoxer Subtask
zippoxer-subtask is a Claude Code plugin for the Build phase that runs subagent tasks in isolated Git worktrees with parallel dispatch orchestration.
by zippoxer · github.com/zippoxer/subtask
Run Claude or Codex subagents on parallel tasks each in its own Git worktree for safer multi-threaded development.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install zippoxer-subtask@zippoxer/subtaskBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:zippoxer/subtask") and the paste-ready config with skillselion.get_install_config("plugin:zippoxer/subtask").
What it does
zippoxer-subtask is a Claude Code plugin built around a skill that breaks your backlog into subtasks executed by subagents inside separate Git worktrees. Solo builders shipping fast with Claude Code or Codex gain isolated workspaces so parallel implementation, experiments, and fixes do not stomp the same branch. The design targets orchestration: dispatch tasks, spin workers, and merge results with clearer boundaries than one monolithic agent session. It fits intermediate users comfortable with git worktree workflows and responsible merge discipline. Use it during Build for feature splits, during Ship when you want review-sized chunks, and during Operate when iteration means many small parallel fixes. This is an agent orchestration plugin, not a hosted CI product or a testing framework—you still own tests, security, and integration. Register the plugin, invoke the subtask skill per repo conventions, and treat each worktree as a short-lived sandbox.
Highlights
- Subtask skill dispatches work to subagents with Git worktree isolation
- Parallel tasks and worker orchestration without shared dirty trees
- Keywords include codex, git-worktrees, dispatch, and isolated workspaces
- Suited to multi-file features split across concurrent agent runs
- Single-plugin repo zippoxer/subtask with 321 GitHub stars
Why builders use it
A single agent branch becomes a bottleneck and conflict magnet when you try to parallelize many coding tasks in one workspace.
After install, you can dispatch subtasks to subagents in dedicated worktrees for parallel, isolated implementation before you merge.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 321 stars, 0 votes.
FAQ
Who is zippoxer-subtask for?
Developers using Claude Code or Codex who want parallel subagent runs isolated in Git worktrees for separate coding tasks.
When should I use zippoxer-subtask?
When you have multiple independent tasks, want worker-style dispatch, and can manage worktrees and merges yourself.
How do I add zippoxer-subtask to my agent?
Install the zippoxer/subtask Claude Code plugin from the repository, register it, then invoke the subtask skill following the repo’s Git worktree setup.
Comments
Share how you use zippoxer-subtask, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.