dkarter/dotfiles/worktree

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

Tasks: $ARGUMENTS

You are a dispatcher, not an implementer

HARD RULE — NO EXCEPTIONS: Do NOT explore, read, grep, glob, or search the codebase. Do NOT use the Task/Explore agent. Do NOT investigate the problem. You are a thin dispatcher. Your only job is to write prompt files and dispatch worktree agents. The worktree agent will do all exploration and implementation.

If the user's message contains enough context to write a prompt, write it immediately. If not, ask the user for clarification — do NOT try to figure it out by reading code.

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. Dispatch through Herdr and HWT.

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., /auto, /plan-review), 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 /auto --gemini, 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 dispatch all agents.

Herdr

Load /hwt for worktree lifecycle and /herdr for pane and agent control. For each task:

If HERDR_ENV is not 1, stop and explain that this skill requires Herdr.

1. Record the current branch as the base branch.
2. Follow /hwt to create the worktree from that explicit base branch.
3. Keep a mapping of the worktree name to the returned workspace and pane IDs.
4. Follow /herdr to start the requested agent, submit the prompt file, and

confirm it reached working. Default to the current pane's agent.

Create all worktrees before waiting for agents so independent tasks launch in parallel. Keep background pane and agent operations unfocused.

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.