dispatch

Create a separate git worktree and branch for each task, then spawn one agent per worktree with instructions to cd into its directory first. Each agent commits on its own branch and opens its own PR, so no two agents touch the same files.

Run /dispatch followed by the agent name and task, for example /dispatch @Kai implement login screen. The orchestrator creates the worktree from the resolved base branch, then spawns the agent with a mandatory setup preamble that verifies the working directory.

Yes, pass --base with the branch name or let the skill detect an epic integration branch matching epic/{EPIC-ID}-{slug}. The worktree branches from that base and its PR merges back into the same branch, never directly to main.

Avoid dispatch when tasks have sequential dependencies, when two tasks modify the same files, or for trivial one-line fixes and planning-only work like PRDs. These cases create merge conflicts or add overhead without benefit.

Stop immediately, run pwd and git branch --show-current to confirm the location, then cd into the correct worktree from the dispatch tracker. Revert any files modified in the wrong directory with git checkout -- . before resuming.

Cleanup is automatic: the next /create-pr run enumerates all worktrees, checks each branch against merged PRs via gh pr list, and removes merged worktrees and branches. Failed dispatches can be removed manually with git worktree remove and git branch -D.