coordinator

Orchestrate parallel git worktree agents via workmux CLI commands.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill coordinator-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinator
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/coordinator
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill coordinator-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI coding agents working in parallel git worktrees is error-prone: prompts lack context, merges conflict, and status tracking is manual. This Skill provides a disciplined dispatch workflow for spawning, monitoring, messaging, and merging worktree agents through the workmux CLI. ## Core Features & Use Cases - Parallel Agent Spawning: Write self-contained prompt files first, then launch all agents in background with workmux add -b -P. - Status Monitoring & Waiting: Track agent states (working, waiting, done) with workmux status, wait, and capture, including timeouts and cross-project handle resolution. - Controlled Merging: Send /merge to agents one at a time, waiting between each to avoid branch conflicts. - Use Case: Split a feature into auth module, API tests, and docs tasks; spawn three worktree agents, wait for completion, review captured output, then merge each branch sequentially. ## Quick Start Ask the coordinator to split your feature into independent tasks and run them as parallel worktree agents with workmux, then merge the results one at a time.

Frequently Asked Questions about coordinator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple Claude Code agents in parallel git worktrees?

Write a self-contained prompt file per task, then spawn each agent with workmux add using the -b background flag and -P prompt file option. Confirm startup with workmux wait --status working before waiting for completion.

How do I monitor background worktree agent status?

Use workmux status for a table of all agents, or workmux wait with handles and a timeout to block until agents finish. Agents report working, waiting, or done states automatically via hooks.

Can workmux send commands to agents in other projects?

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 between repositories.

How do I merge worktree agent branches without conflicts?

Send /merge to one agent at a time with workmux send, then wait for that merge to complete before starting the next. Always review captured output before merging and never merge agents in parallel.

Why should prompt files be written before spawning agents?

Agents cannot see the coordinator's conversation, so prompts must be fully self-contained with relative paths and verbatim context. Writing all files first ensures every agent launches with complete, consistent instructions.