Skill

team

Forces agent team mode to create named teams with tmux split panes, spawning specialized persistent teammates (explorer, hephaestus, oracle) for visible task collaboration instead of background subagents.

developer-tools

automation

npx claudepluginhub erkandogan/oh-my-team

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The user wants a full agent team with visible tmux panes for this task: "$ARGUMENTS"

SKILL.md

Similar Skills

agent-teams

Coordinates multiple Claude Code instances as agent teams for workflows needing inter-agent communication. Covers TeamCreate, SendMessage types, task coordination, hooks, and orchestration patterns.

4 files

majestic-tools

claude-code:agent-team

Orchestrates Claude Code agent teams: spawn teammates, assign tasks with dependencies, manage communication via messages or broadcasts, configure modes, and set quality gate hooks.

3 files7 tools

claude-code

creating-agent-teams

Guides composing agent teams for complex tasks with predefined roles: Orchestrator, Explorer, Frontend (React), Backend (Rails), iOS/Swift, Android/Kotlin, Database.

2 files

creating-agent-teams

Stats

Stars15

Forks0

Last CommitApr 10, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Team Mode — Persistent Agent Team with tmux Panes

The user wants a full agent team with visible tmux panes for this task: "$ARGUMENTS"

You MUST follow these exact steps:

Step 1 — Create the team:

TeamCreate(team_name="descriptive-short-name", description="$ARGUMENTS")

Step 2 — Create tasks for the work:

TaskCreate(subject="Research: ...", description="...") TaskCreate(subject="Implement: ...", description="...")

Step 3 — Spawn teammates INTO the team (use team_name parameter):

For research tasks:

Agent(prompt="Your task: ...", subagent_type="explorer", team_name="the-team-name", name="researcher-1")

For implementation tasks:

Agent(prompt="Your task: ...", subagent_type="hephaestus", team_name="the-team-name", name="builder-1")

For review tasks:

Agent(prompt="Your task: ...", subagent_type="oracle", team_name="the-team-name", name="reviewer-1")

Step 4 — Assign tasks to teammates:

TaskUpdate(taskId="1", owner="researcher-1") TaskUpdate(taskId="2", owner="builder-1")

Step 5 — Coordinate: receive messages, verify results, send follow-ups via SendMessage.

CRITICAL RULES:

You MUST call TeamCreate FIRST — this is what creates the tmux session

Every Agent call MUST include team_name and name parameters

Do NOT use Agent without team_name — that creates subagents, not teammates

Spawn at least 2-3 teammates for the task

Team Mode — Persistent Agent Team with tmux Panes

The user wants a full agent team with visible tmux panes for this task: "$ARGUMENTS"

You MUST follow these exact steps:

Step 1 — Create the team:

TeamCreate(team_name="descriptive-short-name", description="$ARGUMENTS")

Step 2 — Create tasks for the work:

TaskCreate(subject="Research: ...", description="...")
TaskCreate(subject="Implement: ...", description="...")

Step 3 — Spawn teammates INTO the team (use team_name parameter):

For research tasks:

Agent(prompt="Your task: ...", subagent_type="explorer", team_name="the-team-name", name="researcher-1")

For implementation tasks:

Agent(prompt="Your task: ...", subagent_type="hephaestus", team_name="the-team-name", name="builder-1")

For review tasks:

Agent(prompt="Your task: ...", subagent_type="oracle", team_name="the-team-name", name="reviewer-1")

Step 4 — Assign tasks to teammates:

TaskUpdate(taskId="1", owner="researcher-1")
TaskUpdate(taskId="2", owner="builder-1")

Step 5 — Coordinate: receive messages, verify results, send follow-ups via SendMessage.

CRITICAL RULES:

You MUST call TeamCreate FIRST — this is what creates the tmux session
Every Agent call MUST include team_name and name parameters
Do NOT use Agent without team_name — that creates subagents, not teammates
Spawn at least 2-3 teammates for the task