Files
claude-code-best-practice/implementation/claude-agent-teams-implementation.md
T
Shayan Rais 304eab6e52 replace Oishii example with time orchestrator built by agent teams
Agent teams now bootstrap a self-contained time orchestration workflow
inside agent-teams/.claude/ (command, agent, skill). The prompt, diagram,
and How to Use section all reference the new time-orchestrator pattern
with cd agent-teams && claude → /time-orchestrator.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-03-12 18:30:02 +05:00

104 lines
4.7 KiB
Markdown

# Agent Teams Implementation
![Last Updated](https://img.shields.io/badge/Last_Updated-Mar_12%2C_2026-white?style=flat&labelColor=555)
<table width="100%">
<tr>
<td><a href="../">← Back to Claude Code Best Practice</a></td>
<td align="right"><img src="../!/claude-jumping.svg" alt="Claude" width="60" /></td>
</tr>
</table>
---
<a href="#time-orchestration"><img src="../!/tags/implemented-hd.svg" alt="Implemented"></a>
<p align="center">
<img src="assets/impl-agent-teams.png" alt="Agent Teams in action — split pane mode with tmux" width="100%">
</p>
Agent Teams spawn **multiple independent Claude Code sessions** that coordinate via a shared task list. Unlike subagents (isolated context forks within one session), each teammate gets its own full context window with CLAUDE.md, MCP servers, and skills loaded automatically.
---
## ![How to Use](../!/tags/how-to-use.svg)
The time orchestration workflow was built entirely by an agent team. To run the finished product:
```bash
cd agent-teams
claude
/time-orchestrator
```
This invokes the **Command → Agent → Skill** pipeline: the agent fetches Dubai's current time, and the skill renders an SVG time card to `agent-teams/output/dubai-time.svg`.
---
## ![How to Implement](../!/tags/how-to-implement.svg)
You can create a replica of the weather orchestration workflow using agent teams — in this example, the time orchestration workflow was built entirely by an agent team.
### 1. Install [iTerm2](https://iterm2.com/) and tmux
```bash
brew install --cask iterm2
brew install tmux
```
### 2. Start iTerm2 → tmux → Claude
```bash
tmux new -s dev
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude
```
### 3. Prompt with team structure
<a id="time-orchestration"></a>
Paste this prompt into Claude to bootstrap a complete time orchestrator workflow using agent teams:
Main prompt: **[agent-teams-prompt.md](../agent-teams/agent-teams-prompt.md)**
### Team Coordination Flow
```
┌──────────────────────────────────────────────────────────────┐
│ LEAD (You) │
│ "Create an agent team to build time orchestration" │
└──────────────────────────┬───────────────────────────────────┘
│ spawns team (all parallel)
┌────────────┼────────────┐
▼ ▼ ▼
┌────────────────┐ ┌──────────┐ ┌──────────────┐
│ Command │ │ Agent │ │ Skill │
│ Architect │ │ Engineer │ │ Designer │
│ │ │ │ │ │
│ agent-teams/ │ │ agent- │ │ agent-teams/ │
│ .claude/ │ │ teams/ │ │ .claude/ │
│ commands/ │ │ .claude/ │ │ skills/ │
│ time- │ │ agents/ │ │ time-svg- │
│ orchestrator.md│ │ time- │ │ creator/ │
│ │ │ agent.md │ │ │
└───────┬────────┘ └────┬─────┘ └──────┬───────┘
│ │ │
▼ ▼ ▼
┌──────────────────────────────────────────────────┐
│ Shared Task List │
│ ☐ Agree on data contract: {time, tz, formatted} │
│ ☐ Command uses Agent tool (not bash) │
│ ☐ Agent preloads time-fetcher skill │
│ ☐ Skill reads time from context (no re-fetch) │
│ ☐ All files inside agent-teams/.claude/ │
└──────────────────────────────────────────────────┘
┌──────────────────────────────┐
│ cd agent-teams && claude │
│ /time-orchestrator │
│ Command → Agent → Skill │
└──────────────────────────────┘
```