agent teams

AI Community

Skill notes

When to Use This Skill

Use agent teams when... · Use subagents instead when... Multiple agents need to work in parallel · Tasks are sequential and interdependent Ongoing communication between agents is needed · One focused task produces one result Background tasks need progress reporting · Agent output feeds directly into next step Complex workflows benefit from task coordination · Simple, bounded, isolated execution

Sub-Agent Caveat: Spawn Teams from the Main Thread

TeamCreate, Agent, and the related parallel-spawn tools may not be present in a sub-agent's tool surface, even if the parent conversation has them. A sub-agent designed to orchestrate its own team can silently degrade to sequential single-thread execution — same content, much longer wall-clock — without surfacing the failure until its post-completion summary. Authoring guidance: Situation · Recommended pattern

Native Team Tools

Tool · Purpose TeamCreate · Create team and shared task list directory TeamDelete · Clean up team when all work is complete SendMessage · Send DMs, broadcasts, shutdown requests, plan approvals TaskOutput · Get output from a background agent

1. Create the Team

This creates: ~/.claude/teams/<team-name>/ — team config directory ~/.claude/tasks/<team-name>/ — shared task list directory

3. Spawn Teammates

Use the Agent tool to spawn each teammate with the team context:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@laurigates · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview agent-teams-laurigates.preview
# 5. Receive Results

Teammates send messages automatically — they are delivered to the lead's inbox between turns. No polling needed.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.