Orchestrate multiple git worktree agents via workmux CLI commands.
npx skills add https://github.com/okm321/dotfiles --skill coordinator-okm321
Please help me install this Agent Skill. Skill: coordinator Source: https://github.com/okm321/dotfiles/tree/main/claude/skills/coordinator Command: npx skills add https://github.com/okm321/dotfiles --skill coordinator-okm321
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. - Cross-Project Targeting: Address agents in other repositories using global handle resolution or project:handle syntax. - Use Case: Split a feature into backend, tests, and docs tasks, spawn three agents in parallel, wait for all to finish, review their captured output, then merge each branch sequentially. ## Quick Start Ask the AI to coordinate worktree agents by spawning parallel agents for your subtasks, 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 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 each agent the `/merge` command via `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 to avoid conflicts.
Yes, agent commands like send, capture, status, wait, and run resolve handles globally across projects. Use `project:handle` syntax to disambiguate when the same handle name exists in multiple repositories.
The wait command exits with code 1 when the timeout expires before agents reach the target status. Increase the `--timeout` value in seconds, or check `workmux capture` output to see if an agent is stuck or waiting for input.
The coordinator never reads source files or implements tasks itself; it only dispatches and monitors. Agents cannot see the coordinator's conversation, so every prompt file must be fully self-contained with relative paths and verbatim context.
matt-metivierDecompose complex tasks into parallel subtasks and dispatch them across agents.
howdeployAutomate the end-to-end ship workflow from branch to PR.
xvawlValidate Python and TypeScript PRs against linting, typing, tests, and documentation.
aslaiiExecute trivial tasks directly without spawning subagents or creating PLAN.md files.