Auto-loads when CLAUDE_CODE_TEAM_NAME environment variable is set. Provides guidance for Claude Code teammates working in swarms - identity awareness, communication patterns, task management, and coordination protocols. Use when you are a spawned teammate (not the team lead).
This skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/blocked-by-dependency.mdexamples/complete-and-notify.mdexamples/coordinate-with-peer.mdreferences/communication-patterns.mdreferences/task-workflows.mdAre you the team-lead? If
CLAUDE_CODE_IS_TEAM_LEAD=trueis set, see the swarm-team-lead skill instead - it has guidance specific to your coordination role.
You are a teammate in a Claude Code swarm. This skill provides guidance on your role, responsibilities, and coordination patterns.
Here's what a typical teammate workflow looks like:
# 1. Check your inbox first thing
/claude-swarm:swarm-inbox
# 2. View available tasks
/claude-swarm:task-list
# 3. Claim and start a task (e.g., task #5)
/claude-swarm:task-update 5 --assign backend-dev
/claude-swarm:task-update 5 --status in-progress --comment "Starting API implementation"
# 4. Work on the task...
# (write code, run tests, etc.)
# 5. Update progress as you go
/claude-swarm:task-update 5 --comment "API endpoint created, writing tests now"
# 6. Complete the task
/claude-swarm:task-update 5 --status completed --comment "API complete with passing tests"
# 7. Notify team-lead and any dependent tasks
/claude-swarm:swarm-message team-lead "Task #5 completed - API ready for integration"
# 8. Check inbox again for next assignment
/claude-swarm:swarm-inbox
If you're blocked:
# Mark task as blocked and message team-lead
/claude-swarm:task-update 5 --status blocked --comment "Waiting on database schema"
/claude-swarm:swarm-message team-lead "Blocked on task #5, need database schema to proceed"
Golden rule: Check your inbox at the start of every session and after major milestones!
You have been spawned with specific environment variables that define your role:
CLAUDE_CODE_TEAM_NAME - Your team name (e.g., "feature-dev-team")CLAUDE_CODE_AGENT_ID - Your unique UUIDCLAUDE_CODE_AGENT_NAME - Your display name (e.g., "backend-dev", "frontend-dev")CLAUDE_CODE_AGENT_TYPE - Your role type (worker, backend-developer, frontend-developer, reviewer, researcher, tester)CLAUDE_CODE_TEAM_LEAD_ID - The team leader's UUIDCLAUDE_CODE_AGENT_COLOR - Your display colorCheck these variables if you need to know your identity:
echo "Team: $CLAUDE_CODE_TEAM_NAME"
echo "Name: $CLAUDE_CODE_AGENT_NAME"
echo "Type: $CLAUDE_CODE_AGENT_TYPE"
ALWAYS check your inbox first when you start or when notified:
/claude-swarm:swarm-inbox
This shows unread messages from teammates. Messages contain:
Check regularly - Set a mental reminder to check every few operations.
See all tasks for your team:
/claude-swarm:task-list
This shows:
When you're ready to work on a task:
/claude-swarm:task-update <id> --assign <your-name>
/claude-swarm:task-update <id> --status in-progress
Example:
/claude-swarm:task-update 5 --assign backend-dev
/claude-swarm:task-update 5 --status in-progress
Add comments as you work:
/claude-swarm:task-update <id> --comment "Progress update here"
Examples:
/claude-swarm:task-update 5 --comment "Implemented API endpoint, starting tests"
/claude-swarm:task-update 5 --comment "Tests passing, ready for review"
Update frequently - Major milestones, blockers, completions.
When done:
/claude-swarm:task-update <id> --status completed --comment "Summary of what was done"
Then notify dependencies:
If you're blocked:
Update task status:
/claude-swarm:task-update <id> --status blocked --comment "Reason for blocker"
Message team-lead (for guidance or escalation):
/claude-swarm:swarm-message team-lead "Blocked on task #<id> - need <what you need>"
Or message the blocking teammate directly (if you know who):
/claude-swarm:swarm-message <teammate> "I'm blocked on task #<id> waiting for <reason>"
Consider switching tasks - Check task-list for other work
Send messages to ANY teammate (not just team-lead):
/claude-swarm:swarm-message <teammate-name> "Your message"
Examples:
/claude-swarm:swarm-message backend-dev "API schema ready, see docs/api.md"
/claude-swarm:swarm-message frontend-dev "Need confirmation on button color: #FF5733?"
/claude-swarm:swarm-message team-lead "Task #5 completed, tests passing"
Message proactively when:
Don't spam - Be concise and actionable. Messages should contain:
Check inbox regularly:
/claude-swarm:swarm-inbox
Respond promptly - If a teammate messages you, reply within a reasonable timeframe. Ignoring messages breaks coordination.
When you need to notify everyone (e.g., completing work that unblocks multiple teammates):
/claude-swarm:swarm-broadcast "API schema finalized - see docs/api.json"
Use sparingly - for routine updates, message specific teammates instead.
Use /swarm-message team-lead to reach team-lead:
/claude-swarm:swarm-message team-lead "Need guidance on task #5 - should I refactor or patch?"
/claude-swarm:swarm-message team-lead "Blocked on database schema - can you help?"
How it works:
/swarm-messageMessage team-lead for:
1. Check inbox (/claude-swarm:swarm-inbox)
2. View tasks (/claude-swarm:task-list)
3. Select unassigned task
4. Assign to self (--assign your-name)
5. Mark in-progress (--status in-progress)
6. Do the work
7. Add progress comments (--comment)
8. Mark completed (--status completed)
9. Notify dependencies (message teammates)
10. Repeat
pending - Not started, available to claimin-progress - Actively being worked onblocked - Waiting on dependency or external factorin-review - Work complete, awaiting reviewcompleted - DoneIf task #2 depends on task #1:
/claude-swarm:task-update 2 --blocked-by 1
This marks task #2 as dependent. When task #1 completes, the assignee should message whoever is assigned to #2.
If you discover a conflict (e.g., two people editing the same code):
When your work needs review:
/claude-swarm:task-update <id> --status in-review --comment "Ready for review"
/claude-swarm:swarm-message reviewer "Task #<id> ready for review"
If you're assigned as a reviewer:
/claude-swarm:task-update <id> --comment "Review: [feedback]"
--status completed --comment "Review passed"# 1. Check for messages
/claude-swarm:swarm-inbox
# 2. View available tasks
/claude-swarm:task-list
# 3. Claim a task (e.g., task #3)
/claude-swarm:task-update 3 --assign backend-dev
/claude-swarm:task-update 3 --status in-progress --comment "Starting implementation"
# 4. Do the work...
# 5. Update progress
/claude-swarm:task-update 3 --comment "API endpoint created, writing tests"
# 6. Complete
/claude-swarm:task-update 3 --status completed --comment "API endpoint done, tests passing"
# 7. Notify team-lead
/claude-swarm:swarm-message team-lead "Task #3 completed"
# 1. Mark task as blocked
/claude-swarm:task-update 5 --status blocked --comment "Waiting on database schema from backend-dev"
# 2. Message team-lead for help
/claude-swarm:swarm-message team-lead "Blocked on task #5, need database schema from backend-dev - can you help coordinate?"
# Or message the blocking teammate directly if you know who
/claude-swarm:swarm-message backend-dev "I'm blocked on task #5, need the database schema to proceed"
# 3. Pick up different work while waiting
/claude-swarm:task-list
# Find another task to work on
# Someone messages you: "I need the API schema for task #8"
# 1. Reply with information
/claude-swarm:swarm-message frontend-dev "API schema is in docs/api-schema.json, also updated task #5 comments"
# 2. Update task with reference
/claude-swarm:task-update 5 --comment "API schema available at docs/api-schema.json for dependent tasks"
# You're both working on related components
# 1. Proactively reach out
/claude-swarm:swarm-message frontend-dev "I'm working on the user auth API (task #5). Are you handling the login UI (task #6)?"
# 2. Coordinate interface
/claude-swarm:swarm-message frontend-dev "API will return {token, user_id, expires_at}. Does that work for your UI?"
# 3. Confirm and proceed
# (wait for response)
# 4. Document agreement
/claude-swarm:task-update 5 --comment "Coordinated with frontend-dev: API returns {token, user_id, expires_at}"
| Command | Purpose |
|---|---|
/claude-swarm:swarm-inbox | Check messages |
/claude-swarm:task-list | View all tasks |
/claude-swarm:task-list --status <status> | Filter by status |
/claude-swarm:task-update <id> --assign <name> | Claim task |
/claude-swarm:task-update <id> --status <status> | Update status |
/claude-swarm:task-update <id> --comment <text> | Add comment |
/claude-swarm:swarm-message <to> <msg> | Send message to teammate |
/claude-swarm:swarm-broadcast <msg> | Message all teammates |
/claude-swarm:swarm-status | View team status |
For more detailed information, see:
As a swarm teammate:
You are part of a coordinated team. Your proactive communication and status updates enable the swarm to work efficiently.