Auto-sync: 2026-04-21 04:02
This commit is contained in:
44
wiki/concepts/Sequential-Handoffs.md
Normal file
44
wiki/concepts/Sequential-Handoffs.md
Normal file
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: "Sequential Handoffs"
|
||||
type: concept
|
||||
tags: [multi-agent, workflow, coordination]
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
顺序交接(Sequential Handoffs)是一种多智能体工作流模式,其中每个智能体的输出直接作为下一个智能体的输入,按顺序依次传递。
|
||||
|
||||
## Core Principle
|
||||
每个智能体的完整输出(而非摘要)成为下一个智能体的输入,确保信息完整性和上下文连贯性。
|
||||
|
||||
## Workflow Pattern
|
||||
```
|
||||
Agent A → [完整输出] → Agent B → [完整输出] → Agent C
|
||||
```
|
||||
|
||||
## Key Rules
|
||||
- **不摘要,只复制粘贴**:不要总结上一智能体的输出,直接使用完整输出
|
||||
- **保持完整性**:确保所有上下文、细节、证据都传递给下一个智能体
|
||||
- **按顺序执行**:必须等待前一个智能体完成后才能启动下一个
|
||||
|
||||
## Example
|
||||
在 Multi-Agent Workflow: Startup MVP 中:
|
||||
1. Sprint Prioritizer 完成冲刺计划
|
||||
2. 完整计划直接传给 Backend Architect
|
||||
3. Backend Architect 完整输出传给 Frontend Developer
|
||||
|
||||
## Advantages
|
||||
- 最大化信息保留
|
||||
- 减少上下文丢失
|
||||
- 便于追溯和审计
|
||||
|
||||
## Disadvantages
|
||||
- 可能增加处理时间
|
||||
- 需要更多上下文窗口
|
||||
- 顺序执行无法并行加速
|
||||
|
||||
## Related Concepts
|
||||
- [[Parallel Work]]:并行工作模式
|
||||
- [[Quality Gates]]:质量门控
|
||||
- [[Context Passing]]:上下文传递
|
||||
- [[Multi-Agent Team]]:多智能体团队
|
||||
Reference in New Issue
Block a user