Parallel Git Worktree Task Dispatcher

VerifiedCaution

Delegates tasks to parallel agents using Git worktrees. Creates and manages multiple work branches simultaneously through workmux.

Sby Skills Guide Bot
DevelopmentIntermediate
3/9/2026
Claude Code
#git-worktree#parallel-agents#task-delegation#workmux#branch-management

Recommended for

Automated summary

This skill acts as a dispatcher that delegates tasks to parallel agents running in fresh git worktrees via workmux, without ever implementing code itself.

Strengths

  • Cleanly separates dispatching from implementation through a strict dispatcher role
  • Writes detailed prompt files and then runs all workmux commands in parallel to save time
  • Supports delegating to other skills, including passing through flags
  • Handles the --merge option to chain commit, rebase, and merge via the /merge skill

Limitations

  • Depends entirely on the external workmux tool and its prior installation
  • Does not read or edit source files, so it cannot fix an imprecise prompt itself
  • Assumes familiarity with git worktrees and relative paths within each worktree root
When to use it

Use it when you want to launch several independent implementation tasks in parallel across separate git worktrees.

When not to use it

Avoid it for a single task or when workmux is not installed, since it performs no implementation directly.

Security analysis

Caution
Quality score85/100

The skill is not destructive or exfiltrating, and its Bash use is legitimate for creating git worktrees. However, it invokes an external command, writes prompt files, and dispatches agents that can modify code, so it carries meaningful execution risk and should be treated as caution rather than fully safe.

Findings
  • •Uses Bash and Write to create temp prompt files and invoke the external `workmux add` command.
  • •Launches parallel sub-agents with write access to git worktrees, passing user/task content into generated prompts.
  • •Worktree names are interpolated into shell commands; without strict kebab-case sanitation, shell metacharacter injection is possible.
  • •No explicit cleanup of temporary prompt files or failure-handling guidance.
How this analysis is made

Examples

Deux fonctionnalités en parallèle
/worktree Implement user authentication and add a settings page
Déléguer à un skill
/worktree /add-tests --merge Improve coverage for the payments module
Reprendre une option d'une conversation
/worktree Do option 2 from the plan we just discussed

name: worktree description: Delegate tasks to parallel worktree agents. disable-model-invocation: true allowed-tools: Read, Write, Bash, Glob, Grep

Launch one or more tasks in new git worktrees using workmux.

Tasks: $ARGUMENTS

You are a dispatcher, not an implementer

FORBIDDEN: Do NOT read source files, edit code, or fix issues yourself. You only write prompt files and run workmux add commands.

If tasks reference earlier conversation (e.g., "do option 2"), include all relevant context in each prompt you write.

If tasks reference a markdown file (e.g., a plan or spec), re-read the file to ensure you have the latest version before writing prompts.

For each task:

  1. Generate a short, descriptive worktree name (2-4 words, kebab-case)
  2. Write a detailed implementation prompt to a temp file
  3. Run workmux add <worktree-name> -b -P <temp-file> to create the worktree

The prompt file should:

  • Include the full task description
  • Use RELATIVE paths only (never absolute paths, since each worktree has its own root directory)
  • Be specific about what the agent should accomplish

Skill delegation

If the user passes a skill reference (e.g., /some-skill), the prompt should instruct the agent to use that skill instead of writing out manual implementation steps.

Skills can have flags. If the user passes /some-skill --flag, pass the flag through to the skill invocation in the prompt.

Example prompt:

[Task description here]

Use the skill: /skill-name [flags if any] [task description]

Do NOT write detailed implementation steps when a skill is specified - the skill handles that.

Flags

--merge: When passed, add instruction to use /merge skill at the end to commit, rebase, and merge the branch.

...
Then use the /merge skill to commit, rebase, and merge the branch.

Workflow

Write ALL temp files first, THEN run all workmux commands.

Step 1 - Write all prompt files (in parallel):

tmpfile=$(mktemp).md
cat > "$tmpfile" << 'EOF'
Implement feature X...
EOF
echo "$tmpfile"  # Note the path for step 2

Step 2 - After ALL files are written, run workmux commands (in parallel):

workmux add feature-x -b -P /tmp/tmp.abc123.md
workmux add feature-y -b -P /tmp/tmp.def456.md

After creating the worktrees, inform the user which branches were created.

Remember: Your task is COMPLETE once worktrees are created. Do NOT implement anything yourself.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/parallel-git-worktree-task-dispatcher-mmio717t/download' --output '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md.part' && mv '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md.part' '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Bash, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md' && test -s '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/worktree' && cp -R '.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t' '.claude/skills/worktree'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t'

openskills read 'parallel-git-worktree-task-dispatcher-mmio717t'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/parallel-git-worktree-task-dispatcher-mmio717t/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills