isomux-pair-programming

Pair-program a feature with another agent. You drive, they review. Syntax: `/isomux-pair-programming {peer-agent-name} {feature prompt}` Setup: if a peer name was supplied, look up their agent ID via the agent manifest: `curl -s localhost:4000/agents -H "Authorization: Bearer $ISOMUX_AGENT_TOKEN"` (4000 is the default isomux server port; adjust if your office runs on a different one). Match the name case-insensitively. Otherwise try to infer the peer from context — e.g., an agent the boss and you have already paired or consulted with in this session. If there's a clear inference, use it (and briefly confirm who you picked). Otherwise, list candidates (prefer agents whose `cwd` matches yours) and ask the boss to pick. You need the peer's agent ID to POST messages to them. Work in the current cwd unless the boss explicitly asks for a worktree. **Every time you message the peer, include an explicit instruction telling them they must reply by POSTing back to your agent endpoint, not just by writing in their own chat.** Replies that only appear in their own chat never reach you, so the iteration stalls. ### Phase 1: scope (solo) Scope the feature end-to-end by yourself. Read the relevant code, understand what touches what, and gather the context needed to design it. Don't loop in the peer yet. When done, auto-advance to Phase 2. ### Phase 2: design (with peer) Before writing any code, send the peer a short plan: files touched, approach, key edge cases. Ask for feedback. It...