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>
This commit is contained in:
Shayan Rais
Binary file not shown.
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 1.2 MiB |
@@ -11,7 +11,7 @@
|
||||
|
||||
---
|
||||
|
||||
<a href="#asian-fine-dining-app"><img src="../!/tags/implemented-hd.svg" alt="Implemented"></a>
|
||||
<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%">
|
||||
@@ -23,15 +23,22 @@ Agent Teams spawn **multiple independent Claude Code sessions** that coordinate
|
||||
|
||||
## 
|
||||
|
||||
The time orchestration workflow was built entirely by an agent team. To run the finished product:
|
||||
|
||||
```bash
|
||||
tmux new -s oishii
|
||||
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude
|
||||
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`.
|
||||
|
||||
---
|
||||
|
||||
## 
|
||||
|
||||
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
|
||||
@@ -48,89 +55,49 @@ CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude
|
||||
|
||||
### 3. Prompt with team structure
|
||||
|
||||
<a id="asian-fine-dining-app"></a>
|
||||
<a id="time-orchestration"></a>
|
||||
|
||||
```text
|
||||
Create an agent team to build "Oishii" — an Asian fine dining restaurant
|
||||
discovery app. The app lets users browse curated Asian fine dining restaurants,
|
||||
filter by cuisine (Japanese, Chinese, Thai, Korean, Vietnamese, Indian),
|
||||
view chef profiles, read tasting menu details, and make reservations.
|
||||
Paste this prompt into Claude to bootstrap a complete time orchestrator workflow using agent teams:
|
||||
|
||||
Assign these teammates:
|
||||
|
||||
1. **Product Manager** — Define the MVP scope, write user stories for the
|
||||
core flows (browse restaurants, filter by cuisine, view restaurant detail,
|
||||
make a reservation). Create a product spec in docs/product-spec.md with
|
||||
acceptance criteria for each story. Coordinate with other teammates via
|
||||
the shared task list to unblock them.
|
||||
|
||||
2. **Senior Backend Engineer (API)** — Design and implement the REST API
|
||||
using Node.js/Express with TypeScript. Create the data models
|
||||
(Restaurant, Chef, Menu, Reservation), seed data with 12 curated Asian
|
||||
fine dining restaurants across 6 cuisines, and implement endpoints:
|
||||
GET /restaurants (with cuisine filter), GET /restaurants/:id,
|
||||
POST /reservations. Write the API in src/api/.
|
||||
|
||||
3. **Senior Backend Engineer (Database)** — Set up the SQLite database
|
||||
schema with Drizzle ORM. Create migrations, define relations between
|
||||
tables, and implement the repository layer in src/db/. Coordinate with
|
||||
the API engineer via tasks to agree on the data model interface.
|
||||
|
||||
4. **Frontend Engineer** — Build the React frontend with Tailwind CSS in
|
||||
src/app/. Create pages: restaurant listing with cuisine filter chips,
|
||||
restaurant detail with chef bio and tasting menu, and a reservation
|
||||
form modal. Use elegant typography and a dark theme befitting fine dining.
|
||||
Consume the API endpoints defined by the backend team.
|
||||
|
||||
5. **Deployment Engineer** — Set up the project scaffolding (package.json,
|
||||
tsconfig, vite config), Docker Compose for local dev (app + db),
|
||||
and a GitHub Actions CI pipeline (.github/workflows/ci.yml) that runs
|
||||
lint, typecheck, and tests. Write a README.md with setup instructions.
|
||||
|
||||
6. **QA Engineer** — Write end-to-end tests using Vitest for the API
|
||||
(test all endpoints, edge cases like invalid cuisine filter, double
|
||||
booking same time slot) and component tests for the React frontend.
|
||||
Create a test plan in docs/test-plan.md. Run the test suite and
|
||||
report failures to the team via tasks.
|
||||
|
||||
Each teammate should create tasks in the shared task list to coordinate
|
||||
dependencies (e.g., Backend DB must finish schema before API can seed data,
|
||||
API must be running before Frontend can integrate, QA needs both running
|
||||
before e2e tests). Start with Product Manager and Deployment Engineer
|
||||
in parallel, then fan out to the rest.
|
||||
```
|
||||
Main prompt: **[agent-teams-prompt.md](../agent-teams/agent-teams-prompt.md)**
|
||||
|
||||
### Team Coordination Flow
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ LEAD (You) │
|
||||
│ "Create an agent team to build Oishii..." │
|
||||
└──────────────────────────┬──────────────────────────────────┘
|
||||
│ spawns team
|
||||
┌────────────┴────────────┐
|
||||
▼ ▼
|
||||
┌─────────────────┐ ┌──────────────────┐
|
||||
│ Product Manager │ │ Deployment Eng. │
|
||||
│ docs/spec.md │ │ scaffolding, │
|
||||
│ user stories │ │ Docker, CI │
|
||||
└────────┬────────┘ └────────┬─────────┘
|
||||
│ tasks: stories ready │ tasks: project ready
|
||||
▼ ▼
|
||||
┌──────────────────────────────────────────┐
|
||||
│ Shared Task List │
|
||||
│ ☐ Schema defined (DB → API) │
|
||||
│ ☐ Seed data loaded (API) │
|
||||
│ ☐ API endpoints live (API → FE) │
|
||||
│ ☐ UI components done (FE → QA) │
|
||||
└──────────────────────────────────────────┘
|
||||
│ │
|
||||
┌─────────┴──────┐ ┌────────┴────────┐
|
||||
▼ ▼ ▼ ▼
|
||||
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌────────┐
|
||||
│ Backend │ │ Backend │ │ Frontend │ │ QA │
|
||||
│ (DB) │ │ (API) │ │ Engineer │ │Engineer│
|
||||
│ src/db/ │ │ src/api/ │ │ src/app/ │ │ tests/ │
|
||||
└──────────┘ └──────────┘ └────────────┘ └────────┘
|
||||
┌──────────────────────────────────────────────────────────────┐
|
||||
│ 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 │
|
||||
└──────────────────────────────┘
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user