代理团队编排
- 作者仓库星标 1,996
- 作者仓库 openclaw-master-skills
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @LeoYeAI · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Agent Team Orchestration
Production playbook for running multi-agent teams with clear roles, structured task flow, and quality gates.
## Quick Start: Minimal 2-Agent Team
A builder and a reviewer. The simplest useful team.
### 1. Define Roles
```
Orchestrator (you) — Route tasks, track state, report results
Builder agent — Execute work, produce artifacts
```
### 2. Spawn a Task
```
1. Create task record (file, DB, or task board)
2. Spawn builder with:
- Task ID and description
- Output path for artifacts
- Handoff instructions (what to produce, where to put it)
3. On completion: review artifacts, mark done, report
```
### 3. Add a Reviewer
```
Builder produces artifact → Reviewer checks it → Orchestrator ships or returns
```
That's the core loop. Everything below scales this pattern.
## Core Concepts
### Roles
Every agent has one primary role. Overlap causes confusion.
| Role | Purpose | Model guidance |
|------|---------|---------------|
| **Orchestrator** | Route work, track state, make priority calls | High-reasoning model (handles judgment) |
| **Builder** | Produce artifacts — code, docs, configs | Can use cost-effective models for mechanical work |
| **Reviewer** | Verify quality, push back on gaps | High-reasoning model (catches what builders miss) |
| **Ops** | Cron jobs, standups, health checks, dispatching | Cheapest model that's reliable |
→ *Read [references/team-setup.md](references/team-setup.md) when defining a new team or adding agents.*
### Task States
Every task moves through a defined lifecycle:
```
Inbox → Assigned → In Progress → Review → Done | Failed
```
**Rules:**
- Orchestrator owns state transitions — don't rely on agents to update their own status
- Every transition gets a comment (who, what, why)
- Failed is a valid end state — capture why and move on
→ *Read [references/task-lifecycle.md](references/task-lifecycle.md) when designing task flows or debugging stuck tasks.*
### Handoffs
When work passes between agents, the handoff message includes:
1. **What was done** — summary of changes/output
2. **Where artifacts are** — exact file paths
3. **How to verify** — test commands or acceptance criteria
4. **Known issues** — anything incomplete or risky
5. **What's next** — clear next action for the receiving agent
Bad handoff: *"Done, check the files."*
Good handoff: *"Built auth module at `/shared/artifacts/auth/`. Run `npm test auth` to verify. Known issue: rate limiting not implemented yet. Next: reviewer checks error handling edge cases."*
### Reviews
Cross-role reviews prevent quality drift:
- **Builders review specs** — "Is this feasible? What's missing?"
- **Reviewers check builds** — "Does this match the spec? Edge cases?"
- **Orchestrator reviews priorities** — "Is this the right work right now?"
Skip the review step and quality degrades within 3-5 tasks. Every time.
→ *Read [references/communication.md](references/communication.md) when setting up agent communication channels.*
→ *Read [references/patterns.md](references/patterns.md) for proven multi-step workflows.*
## Reference Files
| File | Read when... |
|------|-------------|
| [team-setup.md](references/team-setup.md) | Defining agents, roles, models, workspaces |
| [task-lifecycle.md](references/task-lifecycle.md) | Designing task states, transitions, comments |
| [communication.md](references/communication.md) | Setting up async/sync communication, artifact paths |
| [patterns.md](references/patterns.md) | Implementing specific workflows (spec→build→test, parallel research, escalation) |
## Common Pitfalls
### Spawning without clear artifact output paths
Agent produces great work, but you can't find it. Always specify the exact output path in the spawn prompt. Use a shared artifacts directory with predictable structure.
### No review step = quality drift
"It's a small change, skip review." Do this three times and you have compounding errors. Every artifact gets at least one set of eyes that didn't produce it.
### Agents not commenting on task progress
Silent agents create coordination blind spots. Require comments at: start, blocker, handoff, completion. If an agent goes silent, assume it's stuck.
### Not verifying agent capabilities before assigning
Assigning browser-based testing to an agent without browser access. Assigning image work to a text-only model. Check capabilities before routing.
### Orchestrator doing execution work
The orchestrator routes and tracks — it doesn't build. The moment you start "just quickly doing this one thing," you've lost oversight of the rest of the team.
## When NOT to Use This Skill
- **Single-agent setups** — Just follow standard AGENTS.md conventions. Team orchestration adds overhead that solo agents don't need.
- **One-off task delegation** — Use `sessions_spawn` directly. This skill is for sustained workflows with multiple handoffs.
- **Simple question routing** — If you're just forwarding a question to a specialist, that's a message, not a workflow.
This skill is for **sustained team workflows** — recurring collaboration patterns where agents depend on each other's output over multiple tasks.
章节与文件索引
按说明文件中的顺序排列。
快速入门:最少 2 名代理团队
3. 添加审稿人
角色
任务状态
交接
文件/命令 -> /shared/artifacts/auth/ · npm test auth · sessions_spawn · references/team-setup.md · references/task-lifecycle.md · changes/output · shared/artifacts/auth · references/communication.md
内容校验值 -> cf6366379e6a
当前原文的自动摘译,尚未人工审校。
快速入门:最少 2 名代理团队
构建者和审阅者。最简单有用的团队。
3. 添加审稿人
这就是核心循环。下面的所有内容都遵循这种模式。
角色
每个代理都有一个主要角色。重叠会导致混乱。角色 · 目的 · 模型指导 协调者 · 路由工作、跟踪状态、进行优先级调用 · 高推理模型(处理判断) 构建者 · 生成工件 — 代码、文档、配置 · 可以使用经济高效的模型进行机械工作 审阅者 · 验证质量,缩小差距 · 高推理模型(捕捉构建者错过的内容)
任务状态
每个任务都会经历一个定义的生命周期: 规则:Orchestrator 拥有状态转换 — 不依赖代理来更新自己的状态 每个转换都会有一条注释(谁、什么、为什么) 失败是一个有效的最终状态 — 捕获原因并继续
交接
当工作在代理之间传递时,移交消息包括: 做了什么 - 更改/输出摘要 工件在哪里 - 确切的文件路径 如何验证 - 测试命令或验收标准 已知问题 - 任何不完整或有风险的事情