From claude-swarm
Auto-loads when CLAUDE_CODE_IS_TEAM_LEAD environment variable is set. Provides guidance for spawned team-leads on monitoring teammates, handling consults, assigning tasks, and coordinating the team. Use this when you are a spawned team-lead (not the original orchestrator who created the swarm).
npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-1 --plugin und3rf10w-claude-litterThis skill uses the workspace's default tool permissions.
You are a **spawned team-lead** in a Claude Code swarm. This skill provides guidance on your responsibilities and how to coordinate your team effectively.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
You are a spawned team-lead in a Claude Code swarm. This skill provides guidance on your responsibilities and how to coordinate your team effectively.
As team-lead, you are responsible for:
You are NOT a worker - you coordinate and support the team.
# 1. Check your inbox (teammates may have messaged you)
/claude-swarm:swarm-inbox
# 2. View team status
/claude-swarm:swarm-status
# 3. View tasks and assignments
/claude-swarm:task-list
# 4. Respond to any teammate messages
/claude-swarm:swarm-message <teammate> "Your response"
ALWAYS check your inbox frequently - teammates consult you for guidance:
/claude-swarm:swarm-inbox
Teammates reach you via /swarm-message team-lead which sends a message to your inbox.
Be responsive - teammates depend on you to stay unblocked.
Check overall team health:
/claude-swarm:swarm-status
Shows:
See all tasks:
/claude-swarm:task-list
Filter to focus on what matters:
# In-progress work
/claude-swarm:task-list --status in_progress
# Blocked tasks (need attention!)
/claude-swarm:task-list --blocked
# Specific teammate's tasks
/claude-swarm:task-list --owner backend-dev
When tasks need assignment:
/claude-swarm:task-update <id> --assign <teammate-name>
Example:
/claude-swarm:task-update 3 --assign frontend-dev
Message a specific teammate:
/claude-swarm:swarm-message <teammate> "<message>"
Broadcast to everyone:
/claude-swarm:swarm-broadcast "<message>"
Trigger inbox checks (useful after sending messages):
/claude-swarm:swarm-send-text <teammate> "/swarm-inbox\r"
/claude-swarm:swarm-send-text all "/swarm-inbox\r"
If the team needs more help:
/claude-swarm:swarm-spawn "<name>" "<type>" "<model>" "<prompt>"
Example:
/claude-swarm:swarm-spawn "qa-engineer" "tester" "sonnet" "You are the QA engineer. Write tests for the auth system. Check task list for details."
Verify spawn succeeded:
/claude-swarm:swarm-verify
When teammates message you, you'll see their message in your inbox.
Respond promptly:
# Check what they asked
/claude-swarm:swarm-inbox
# Respond
/claude-swarm:swarm-message backend-dev "Yes, use the existing auth middleware. See src/middleware/auth.ts"
Common consult types:
| Type | How to Handle |
|---|---|
| Question | Answer directly via /swarm-message |
| Blocker | Help unblock or reassign work |
| Decision needed | Make the call and communicate it |
| Scope issue | Clarify requirements |
When a teammate is blocked:
# Message the blocking teammate
/claude-swarm:swarm-message api-designer "frontend-dev is waiting on the API schema. ETA?"
# Once unblocked, notify
/claude-swarm:swarm-message frontend-dev "API schema is ready at docs/api.json. You're unblocked."
External agents may discover and request to join your team. You'll see join requests in your inbox:
# Check inbox for join requests
/claude-swarm:swarm-inbox
# You'll see: "JOIN REQUEST: Agent 'external-agent' requesting to join as 'worker'. Request ID: abc123..."
# Approve with custom name
/claude-swarm:swarm-approve-join abc123 new-backend-dev blue
# Or reject with reason
/claude-swarm:swarm-reject-join abc123 "Team at capacity"
When to approve:
When to reject:
When you need to shutdown a specific teammate:
# Request graceful shutdown (allows them to finish current work)
/claude-swarm:swarm-request-shutdown backend-dev "Task completed, cleaning up team"
The teammate will receive the shutdown request in their inbox and can acknowledge before stopping.
For team-wide shutdown, the orchestrator uses:
# Graceful team cleanup (sends shutdown requests to all)
/claude-swarm:swarm-cleanup <team> --graceful
| Command | Purpose |
|---|---|
/claude-swarm:swarm-inbox | Check messages from teammates |
/claude-swarm:swarm-status | View team status |
/claude-swarm:task-list | View all tasks |
/claude-swarm:task-list --blocked | Find blocked tasks |
/claude-swarm:task-update <id> --assign <name> | Assign task |
/claude-swarm:swarm-message <to> <msg> | Message teammate |
/claude-swarm:swarm-broadcast <msg> | Message all |
/claude-swarm:swarm-send-text <target> <text> | Send to terminal |
/claude-swarm:swarm-spawn <name> <type> <model> <prompt> | Spawn teammate |
/claude-swarm:swarm-verify | Verify teammates alive |
/claude-swarm:swarm-approve-join <id> | Approve join request |
/claude-swarm:swarm-reject-join <id> | Reject join request |
/claude-swarm:swarm-request-shutdown <agent> | Request graceful shutdown |
You have these environment variables set:
| Variable | Description |
|---|---|
CLAUDE_CODE_TEAM_NAME | Your team name |
CLAUDE_CODE_AGENT_NAME | team-lead |
CLAUDE_CODE_IS_TEAM_LEAD | true |
CLAUDE_CODE_AGENT_ID | Your unique UUID |