superteam multiplexer-spawn

Name: superteam multiplexer-spawn
Availability: InStock
Author: ahmedelbanna80

Spawn superteam teammates in the correct terminal multiplexer pane.

Updated May 13, 2026

Search Tags:#claude code #tmux #iterm2 #agent spawning #cmux #terminal multiplexers #pane title

Ready to run

npx skills add https://github.com/AhmedElBanna80/superteam --skill superteam-multiplexer-spawn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superteam multiplexer-spawn
Source: https://github.com/AhmedElBanna80/superteam/tree/main/skills/multiplexer-spawn
Command: npx skills add https://github.com/AhmedElBanna80/superteam --skill superteam-multiplexer-spawn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It solves the problem of reliably starting the correct superteam teammate inside the appropriate terminal environment so each teammate gets its own pane/window and the workflow stays organized by ticket and role.

Core Features & Use Cases

Multiplexer auto-detection: Detects cmux, tmux, iTerm2, or falls back to in-process when none is available.
Correct pane/window spawning: Opens a new split/window/surface and launches Claude Code in it using the right backend for the active multiplexer.
Pane title discipline: Sets the pane title to <ticket>:<role> immediately on startup to support by-worktree grouping and clear routing.

Quick Start

Tell the lead to process a ticket like AUTH-1: "add login form with email validation" and the planner will spawn the implementer, spec reviewer, and code reviewer in the correct terminal panes with titles set for <ticket>:<role>.

Frequently Asked Questions about superteam multiplexer-spawn

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

FAQPage Schema

How do I spawn Claude Code agents in separate terminal panes automatically?▼

To spawn Claude Code agents in separate terminal panes, this skill auto-detects your active multiplexer like tmux, cmux, or iTerm2 and opens a new split or window to launch each teammate in its own isolated environment.

Does terminal pane spawning work with tmux and iTerm2?▼

Pane spawning works with tmux and iTerm2 by applying backend-specific launch behavior that detects your runtime environment and opens a dedicated surface for each agent to keep workflows organized.

How do I set terminal pane titles dynamically based on ticket and role?▼

You can set terminal pane titles dynamically using OSC escape sequences immediately on agent startup, formatting the title as ticket:role to support clear routing and by-worktree grouping across your multiplexer panes.

What environment variables are needed to detect terminal multiplexers for agent spawning?▼

Multiplexer detection requires checking the CMUX_WORKSPACE_ID, TMUX, and TERM_PROGRAM environment variables to identify the active backend and apply the correct launch behavior for spawning Claude Code teammates.

Can I manually spawn a specific teammate like a code reviewer in tmux?▼

You can manually spawn a specific teammate such as a code reviewer in tmux by issuing an explicit spawn request, which triggers the backend-specific launch behavior to open the pane and set the role title.

What happens when ISSUES_FOUND triggers a respawn in the terminal multiplexer?▼

When ISSUES_FOUND is triggered during a planner-driven ticket workflow, the skill respawns the required teammate in the correct multiplexer pane, resetting the pane title to the ticket and role for continued tracking.