Zippoxer Subtask
- 338 repo stars
- Updated April 27, 2026
- zippoxer/subtask
zippoxer-subtask is a Claude Code plugin that runs subagent tasks in isolated Git worktrees with parallel dispatch orchestration.
About
zippoxer-subtask is a Claude Code plugin built around a skill that breaks your backlog into subtasks executed by subagents inside separate Git worktrees. developers 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.
- 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
Zippoxer Subtask by the numbers
- Data as of Jul 26, 2026 (Skillselion catalog sync)
/plugin install zippoxer-subtask@zippoxer/subtaskAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 338 |
|---|---|
| Last updated | April 27, 2026 |
| Repository | zippoxer/subtask ↗ |
What it does
Run Claude or Codex subagents on parallel tasks each in its own Git worktree for safer multi-threaded development.
Who is it for?
Best when you use Claude Code or Codex and already use Git and want parallel agent tasks without branch chaos.
Skip if: Non-Git projects, developers who never use worktrees, or teams that need managed cloud CI instead of local agent orchestration.
What you get
After install, you can dispatch subtasks to subagents in dedicated worktrees for parallel, isolated implementation before you merge.
- Subtask skill available for dispatching parallel agent work
- Isolated per-task Git worktrees for subagent implementations
- Orchestration patterns documented in zippoxer/subtask
By the numbers
- GitHub stars: 321
- pluginCount: 1
- Repository: zippoxer/subtask
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Git-worktree subagent orchestration skill, not a quant data plugin or generic happy-skills productivity pack.
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.