implement-agent-teams
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Set up and validate Claude agent team configurations, collaboration flows, and operator guidance for team-based execution.
In this repository8 other files it gives its agents.
- implement-agent-skillsSkill
- implement-claude-extensionsSkill
- implement-hooksSkill
- implement-pluginSkill
- implement-sub-agentsSkill
- lint-fixSkill
- plugin-implementation-deprecatedSkill
- plugin-verificationSkill
The file
Files
Implement Agent Teams
Implement team setup and coordination patterns for multi-agent workflows, including display modes and operational constraints.
Workflow
- Validate complexity: Confirm team is needed (score 9-10). Can multiple specialized sub-agents work independently?
- Define team objective: Clear goal requiring coordinated multi-agent execution
- Identify members: Specialized agents with non-overlapping responsibilities
- Set boundaries: Clear ownership and handoff contracts between agents
- Configure metadata: Team metadata and task routing conventions
- Plan coordination: Sequential vs parallel execution patterns
- Document rules: Coordination rules and display mode choices
- Evaluation strategy: How to test team-based workflows (20-50 scenarios)
- Run checks: Environment and config validation
- Verify fallbacks: Limitations and fallback behavior
Progressive Disclosure
Best Practices (Anthropic Guidelines)
- Complexity decision framework:
../implement-claude-extensions/references/decision-framework.md - Context management patterns:
../implement-claude-extensions/references/context-management.md - Evaluation strategy:
../implement-claude-extensions/references/evaluation-strategy.md
Team Design
- Team setup structure:
references/team-setup.md - Coordination contracts:
references/team-coordination.md - Display mode selection:
references/team-display-modes.md - Team best practices:
references/team-best-practices.md - Known limitations:
references/team-limitations.md
Validation Tools
- Team config checker:
scripts/check-team-config.sh - Environment verifier:
scripts/verify-team-env.sh
Templates
- Team config example:
assets/templates/team-config-example.json - Team task example:
assets/templates/team-task-example.md
Related Skills
- Umbrella routing and component comparison:
../implement-claude-extensions/SKILL.md - Sub-agent design:
../implement-sub-agents/SKILL.md
Sources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

