Orchestrate multiple git worktree agents via workmux CLI commands.
npx skills add https://github.com/pattobrien/dotfiles --skill coordinator-pattobrien
Please help me install this Agent Skill. Skill: coordinator Source: https://github.com/pattobrien/dotfiles/tree/main/claude/skills/coordinator Command: npx skills add https://github.com/pattobrien/dotfiles --skill coordinator-pattobrien
workmux add, each in its own git worktree and branch. - Monitoring & Communication: Check agent statuses, wait for completion with timeouts, capture output, and send follow-up instructions or skill commands like /merge. - Fan-out / Fan-in Workflows: Spawn several agents in parallel, wait for all to finish, review captured output, then merge branches one at a time to avoid conflicts. - Use Case: You need an auth module, API tests, and docs updated simultaneously. The coordinator writes three prompt files, spawns three worktree agents, waits for completion, reviews each output, and sequentially triggers merges. ## Quick Start Ask the AI to coordinate worktree agents by spawning a background agent for each task, waiting for them to finish, and merging their branches one at a time.High-intent search queries and answers about installing and using this skill.
Write a self-contained prompt file for each task, then spawn background agents with `workmux add <handle> -b -P <file>`. Each agent runs in its own git worktree and tmux window, and you monitor them with `workmux status` and `workmux wait`.
Send `/merge` to each agent with `workmux send <handle> "/merge"` so the agent handles rebasing and conflict resolution itself. Merge one agent at a time and wait for each to finish before starting the next to avoid conflicts.
Yes, agent commands like send, capture, status, wait, and run resolve handles globally across projects. Use the `project:handle` syntax to disambiguate when worktree names collide, while lifecycle commands like add and remove stay repo-scoped.
Exit code 1 means the timeout was reached, 2 means the worktree was not found, and 3 means the agent exited unexpectedly. Always pass `--timeout` and handle these exit codes gracefully in coordination workflows.
Agents cannot see the coordinator's conversation, so prompt files must be fully self-contained with verbatim context and relative paths. The coordinator must never edit source files directly and should not delegate skills unless explicitly instructed.
gelowzzzConvert planning conversations into structured feature spec folders with task files.
GenEducationPrepare feature branches for release with tests, versioning, and pull requests.
microsoftAutomates pre-PR verification, code review, and pull request creation for completed feature branches.
m16khbDispatch fresh subagents per task with code review and test gates.