agent-team-driven-development

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Agent Team Driven Development for Plan Execution

基于Agent Team驱动的计划执行开发

Coordinate multiple specialized teammates working in parallel to execute complex implementation plans.

协调多个专业协作成员并行工作，以执行复杂的实施计划。

Agent Teams vs Sub-agents

Choose based on whether workers need to communicate with each other.

Dimension	Sub-agents	Agent Teams
Communication	Results return to caller only	Teammates message each other directly
Coordination	Main agent manages all work	Shared task list with self-coordination
Best for	Focused tasks where only the result matters	Complex work requiring discussion and collaboration
Token cost	Lower	Higher: each teammate is a separate instance

Use Sub-agents for independent tasks needing no inter-worker communication (research, validation, file search). Use Agent Teams when teammates must share findings, challenge each other, or self-coordinate across 3+ parallel work streams. For sequential or highly interdependent tasks, use a single session.

根据协作成员是否需要相互沟通来进行选择。

维度	Sub-agents	Agent Teams
沟通方式	仅将结果返回给调用方	协作成员之间直接发送消息
协调机制	主Agent管理所有工作	共享任务列表，自主协调
适用场景	仅关注结果的聚焦型任务	需要讨论与协作的复杂工作
Token成本	较低	较高：每个协作成员都是独立实例

当任务独立、无需协作成员间沟通时（如调研、验证、文件搜索），使用Sub-agents。当协作成员必须共享发现成果、相互探讨，或需要在3个及以上并行工作流中自主协调时，使用Agent Teams。对于顺序执行或高度依赖的任务，使用单个会话即可。

Execution Workflow

执行工作流

Analyze plan -- identify task independence, file conflicts, and required roles (Implementer, Reviewer, Architect)
Spawn team -- provide each teammate with task assignments, file paths, constraints, and verification criteria. Teammates do not inherit conversation history.
Coordinate -- monitor via shared task list, facilitate cross-teammate communication, use delegate mode (
```
Shift+Tab
```
) to keep the lead focused on coordination
Verify and clean up -- validate integration, run tests, shut down teammates, clean up team resources via the lead

See

./references/initiate-team-workflow.md

and

./references/manage-team-workflow.md

for detailed workflows.

分析计划 —— 识别任务独立性、文件冲突以及所需角色（Implementer、Reviewer、Architect）
组建团队 —— 为每个协作成员分配任务、文件路径、约束条件和验证标准。协作成员不会继承对话历史。
协调工作 —— 通过共享任务列表进行监控，促进协作成员间的沟通，使用委托模式（
```
Shift+Tab
```
）让主导者专注于协调工作
验证与收尾 —— 验证集成效果、运行测试、关闭协作成员实例，通过主导者清理团队资源

详细工作流请参阅

./references/initiate-team-workflow.md

和

./references/manage-team-workflow.md

。

Roles

角色定义

Implementer: executes coding tasks on assigned files, follows TDD/BDD. See
```
./references/implementer-role.md
```
.
Reviewer: validates quality, security, and plan compliance. See
```
./references/reviewer-role.md
```
.
Architect: resolves cross-cutting concerns, maintains system-wide consistency. See
```
./references/architect-role.md
```
.

Implementer（实现者）：负责在指定文件上执行编码任务，遵循TDD/BDD规范。详情请参阅
```
./references/implementer-role.md
```
。
Reviewer（审核者）：验证质量、安全性以及计划合规性。详情请参阅
```
./references/reviewer-role.md
```
。
Architect（架构师）：解决跨领域问题，维护系统全局一致性。详情请参阅
```
./references/architect-role.md
```
。

Key Practices

关键实践

Assign distinct file ownership per teammate to prevent edit conflicts
Include 5-6 tasks per teammate for steady throughput
Document task dependencies explicitly so blocked tasks wait automatically
Provide full context in spawn prompts (file paths, goals, constraints)
Require verification evidence (test results, etc.) upon task completion
Monitor frequently; unattended teams risk wasted effort

For architecture, capabilities, and limitations, see

./references/official-documentation.md

为每个协作成员分配明确的文件所有权，避免编辑冲突
为每个协作成员分配5-6项任务，以保证稳定的工作产出
明确记录任务依赖关系，使被阻塞的任务自动等待
在组建团队的提示中提供完整上下文（文件路径、目标、约束条件）
要求任务完成时提供验证依据（如测试结果等）
频繁监控；无人看管的团队可能会造成工作浪费

关于架构、功能和限制，请参阅

./references/official-documentation.md

。