Team

Usage

In Qwen Code Chat

/skill:team 3:executor "Fix all TypeScript errors in src/"

When invoked, the agent should:

1. Parse the N:role and task from the request
2. Execute the team command in the terminal
3. Report back the team name and monitoring commands

Terminal Command (Direct)

# Preferred - spawns tmux panes immediately
team 3:executor "Fix TypeScript errors"
team 4:reviewer "Review all open PRs"
team 5:tester "Write integration tests"

Process (What Actually Happens)

When team command executes:

1. tmux Session Creation

   • Splits current tmux window into N panes
   • Each pane gets an independent Qwen Code session

2. Worker Initialization

   • Creates .qmx/state/team/<team>/config.json
   • Creates worker identity files
   • Creates inbox.md with assignments

3. Central Messaging

   • Mailbox: .qmx/state/team/<team>/mailbox/
   • Heartbeat: .qmx/state/team/<team>/workers/worker-N/heartbeat.json
   • Leader nudge via tmux display-message

4. Parallel Execution

   • Each worker operates independently
   • Workers report via mailbox files
   • Leader monitors progress

Output Structure

Team state is tracked in .qmx/state/team/<team-name>/:

.qmx/state/team/team-1771604000-abc/
├── config.json           # Team configuration
├── worker-agents.md      # Worker instructions
├── mailbox/              # Central messaging
│   ├── worker-1.json
│   ├── worker-2.json
│   └── leader-fixed.json
├── workers/
│   ├── worker-1/
│   │   ├── identity.json
│   │   ├── inbox.md
│   │   └── heartbeat.json
│   └── worker-2/
└── tasks/
    └── task-1.json

Examples

Example 1: Fix Errors

User: /skill:team 3:executor "Fix all TypeScript errors in src/"

Agent should execute:

team 3:executor "Fix all TypeScript errors in src/"

Agent should report:

🚀 Team launched!

Team: team-1771604000-abc123
Workers: 3
Role: executor
Task: Fix all TypeScript errors in src/

Monitor: qmx team status team-1771604000-abc123
Stop: qmx team shutdown team-1771604000-abc123

Example 2: Code Review

User: /skill:team 4:reviewer "Review all open PRs"

Agent should execute:

team 4:reviewer "Review all open PRs"

Example 3: With Ralph Mode

User: /skill:team ralph 2:planner "Plan the database migration"

Agent should execute:

team ralph 2:planner "Plan the database migration"

Available Roles

• executor - Implementation and code generation
• reviewer - Code review and quality assurance
• tester - Test generation and execution
• debugger - Bug investigation and fixing
• refactorer - Code refactoring
• documenter - Documentation generation
• architect - System design review
• planner - Task decomposition

Monitoring Commands

# Check team status
qmx team status <team-name>

# List all teams
qmx team list

# Shutdown team
qmx team shutdown <team-name>

# View mailbox (advanced)
cat .qmx/state/team/<team>/mailbox/*.json

Requirements

• tmux >= 3.0 installed
• Running inside tmux session ($TMUX is set)
• QMX installed globally
• Node.js >= 20

Troubleshooting

"Not running inside tmux"

# Start tmux first
tmux

# Then run team command
team 3:executor "task"

"command not found: team"

# Ensure PATH includes ~/bin
export PATH="$HOME/bin:$HOME/.local/bin:$PATH"

Team starts but workers don't respond

# Check worker panes
tmux list-panes -F '#{pane_id}\t#{pane_current_command}'

# Check mailbox
cat .qmx/state/team/<team>/mailbox/*.json

# Check heartbeats
cat .qmx/state/team/<team>/workers/*/heartbeat.json

Related Skills

• plan - Plan work before executing with team
• review - Review team output
• status - Check team status
• cancel - Cancel team execution

CRITICAL: This skill MUST execute the team command in the terminal, not just describe it!