中文译文

智能体组织

通过系统化的任务分析、能力映射和工作流设计，组建并协调多智能体团队。

配置

智能体数量：${agent_count:3}
任务类型：${task_type:general}
编排模式：${orchestration_pattern:parallel}
最大并发数：${max_concurrency:5}
超时时间（秒）：${timeout_seconds:300}
重试次数：${retry_count:3}

核心流程

分析需求：理解任务范围、约束条件和成功标准
映射能力：将可用智能体与所需技能进行匹配
设计工作流：创建包含依赖关系和检查点的执行计划
编排执行：协调 ${agent_count:3} 个智能体并监控进度
持续优化：根据性能反馈进行调整

任务分解

需求分析

将复杂任务拆解为离散的子任务
确定每个子任务的输入/输出要求
估算每个组件的复杂度和资源需求
为每个单元定义明确的成功标准

依赖关系映射

记录任务执行顺序的约束条件
确定子任务之间的数据依赖关系
映射资源共享需求
检测潜在的瓶颈和冲突

时间线规划

按照依赖关系对任务进行排序
识别可并行化的机会（最多 ${max_concurrency:5} 个并发）
为高风险组件分配缓冲时间
定义用于进度验证的检查点

智能体选择

能力匹配

根据以下因素选择智能体：

所需技能与智能体专长的匹配程度
在类似任务上的历史表现
当前可用性和工作负载容量
针对任务复杂度的成本效益

选择标准优先级

能力匹配：智能体必须具备所需技能
过往记录：优先选择有成功经验的智能体
可用性：有足够能力按时完成
成本：在约束条件内优化资源利用

备份规划

为关键角色确定备用智能体
定义故障转移触发条件和交接流程
为单点故障任务保持冗余

团队组建

组成原则

确保对所有子任务实现完整技能覆盖
在 ${agent_count:3} 个团队成员之间平衡工作负载
最小化沟通开销
为关键功能加入冗余

角色分配

根据优势将智能体匹配到子任务
定义明确的所有权和问责制
在相互依赖的角色之间建立沟通渠道
记录阻塞问题的升级路径

团队规模

对于紧耦合任务使用较小团队
对于可并行工作负载使用较大团队
在规模决策中考虑协调开销
根据进展动态扩展

编排模式

顺序执行

当任务有严格顺序要求时使用：

任务 B 需要任务 A 的输出
步骤之间状态必须保持一致
错误处理需要有序回滚

并行处理

当任务相互独立时使用（${orchestration_pattern:parallel}）：

任务之间没有数据依赖
资源需求相互独立
结果可在完成后聚合
最大 ${max_concurrency:5} 个并发操作

流水线模式

用于流式或持续处理：

每个阶段处理并转发结果
支持不同阶段的并发执行
降低多步骤工作流的整体延迟

分层委派

用于需要子编排的复杂任务：

主导智能体协调子团队
每个子团队处理一个领域
结果通过层级向上聚合

Map-Reduce

用于大规模数据处理：

Map 阶段将工作分配到各个 agent
每个 agent 处理一个分区
Reduce 阶段合并结果

工作流设计

流程结构

入口点：验证输入并初始化状态
执行阶段：有序的任务分组
检查点：状态持久化与验证点
出口点：结果聚合与清理

控制流

为备选路径定义分支条件
为瞬时故障指定重试策略（最多 ${retry_count:3} 次重试）
为每个阶段设定超时阈值（默认 ${timeout_seconds:300}%PH_22%%）
为部分失败规划优雅降级

数据流

记录各阶段之间的数据转换
指定数据格式与验证规则
规划检查点处的数据持久化
处理完成后的数据清理

协调策略

通信模式

直接：agent 对 agent，用于紧耦合
广播：一对多，用于状态更新
基于队列：异步，用于解耦任务
事件驱动：对状态变化作出反应

同步

为依赖任务定义同步点
实现带超时的等待机制（${timeout_seconds:300}%PH_23%%）
优雅处理乱序完成
在各 agent 之间保持一致状态

冲突解决

为资源争用建立优先级规则
为冲突定义仲裁机制
记录死锁的回滚流程
通过精心调度预防冲突

性能优化

负载均衡

根据 agent 容量分配工作
监控利用率并动态再平衡
避免使高性能 agent 过载
对数据密集型任务考虑 agent 局部性

瓶颈管理

通过监控识别缓慢阶段
为受限资源增加容量
重构工作流以减少依赖
在有益处缓存中间结果

资源效率

跨智能体共享资源池
使用后及时释放资源
批量处理相似操作以减少开销
监控资源浪费并发出告警

监控与自适应

进度跟踪

监控每个任务的完成状态
跟踪实际耗时与预估时间的对比
识别有延迟风险的任务
向利益相关者报告汇总进度

性能指标

任务完成率和延迟
智能体利用率和吞吐量
错误率和恢复时间
资源消耗和成本

动态调整

根据进度重新分配智能体
根据阻塞情况调整优先级
根据工作负载调整团队规模
根据经验教训修改工作流

错误处理

故障检测

监控任务失败和超时（${timeout_seconds:300}%PH_24%% 阈值）
及时检测智能体不可用
识别级联故障模式
对异常行为发出告警

恢复流程

对瞬时故障进行退避重试（最多 ${retry_count:3} 次尝试）
在需要时故障转移到备用智能体
在严重故障时回滚到上一个检查点
升级无法恢复的问题

预防

在执行前验证输入
在分配前测试智能体可用性
设计优雅降级方案
在关键路径中构建冗余

质量保证

验证关卡

在每个检查点验证输出
交叉检查并行任务的结果
验证最终汇总结果
确认满足成功标准

性能标准

智能体选择准确率目标：>${agent_selection_accuracy:95}%
任务完成率目标：>${task_completion_rate:99}%
响应时间目标：<${response_time_threshold:5} 秒
资源利用率：最佳范围 ${utilization_min:60}-${utilization_max:80}%

最佳实践

规划

投入时间进行全面的任务分析
记录假设和约束条件
提前规划故障场景
定义明确的成功指标

执行

从最小可行团队开始（${agent_count:3} 个智能体）
根据观察到的需求进行扩展
保持清晰的沟通渠道
对照里程碑跟踪进展

学习

捕获性能数据以供分析
识别成功与失败中的模式
优化选择与协调策略
在未来的编排中共享经验教训

English original

Agent Organization

Assemble and coordinate multi-agent teams through systematic task analysis, capability mapping, and workflow design.

Configuration

Agent Count: ${agent_count:3}
Task Type: ${task_type:general}
Orchestration Pattern: ${orchestration_pattern:parallel}
Max Concurrency: ${max_concurrency:5}
Timeout (seconds): ${timeout_seconds:300}
Retry Count: ${retry_count:3}

Core Process

Analyze Requirements: Understand task scope, constraints, and success criteria
Map Capabilities: Match available agents to required skills
Design Workflow: Create execution plan with dependencies and checkpoints
Orchestrate Execution: Coordinate ${agent_count:3} agents and monitor progress
Optimize Continuously: Adapt based on performance feedback

Task Decomposition

Requirement Analysis

Break complex tasks into discrete subtasks
Identify input/output requirements for each subtask
Estimate complexity and resource needs per component
Define clear success criteria for each unit

Dependency Mapping

Document task execution order constraints
Identify data dependencies between subtasks
Map resource sharing requirements
Detect potential bottlenecks and conflicts

Timeline Planning

Sequence tasks respecting dependencies
Identify parallelization opportunities (up to ${max_concurrency:5} concurrent)
Allocate buffer time for high-risk components
Define checkpoints for progress validation

Agent Selection

Capability Matching

Select agents based on:

Required skills versus agent specializations
Historical performance on similar tasks
Current availability and workload capacity
Cost efficiency for the task complexity

Selection Criteria Priority

Capability fit: Agent must possess required skills
Track record: Prefer agents with proven success
Availability: Sufficient capacity for timely completion
Cost: Optimize resource utilization within constraints

Backup Planning

Identify alternate agents for critical roles
Define failover triggers and handoff procedures
Maintain redundancy for single-point-of-failure tasks

Team Assembly

Composition Principles

Ensure complete skill coverage for all subtasks
Balance workload across ${agent_count:3} team members
Minimize communication overhead
Include redundancy for critical functions

Role Assignment

Match agents to subtasks based on strength
Define clear ownership and accountability
Establish communication channels between dependent roles
Document escalation paths for blockers

Team Sizing

Smaller teams for tightly coupled tasks
Larger teams for parallelizable workloads
Consider coordination overhead in sizing decisions
Scale dynamically based on progress

Orchestration Patterns

Sequential Execution

Use when tasks have strict ordering requirements:

Task B requires output from Task A
State must be consistent between steps
Error handling requires ordered rollback

Parallel Processing

Use when tasks are independent (${orchestration_pattern:parallel}):

No data dependencies between tasks
Separate resource requirements
Results can be aggregated after completion
Maximum ${max_concurrency:5} concurrent operations

Pipeline Pattern

Use for streaming or continuous processing:

Each stage processes and forwards results
Enables concurrent execution of different stages
Reduces overall latency for multi-step workflows

Hierarchical Delegation

Use for complex tasks requiring sub-orchestration:

Lead agent coordinates sub-teams
Each sub-team handles a domain
Results aggregate upward through hierarchy

Map-Reduce

Use for large-scale data processing:

Map phase distributes work across agents
Each agent processes a partition
Reduce phase combines results

Workflow Design

Process Structure

Entry point: Validate inputs and initialize state
Execution phases: Ordered task groupings
Checkpoints: State persistence and validation points
Exit point: Result aggregation and cleanup

Control Flow

Define branching conditions for alternative paths
Specify retry policies for transient failures (max ${retry_count:3} retries)
Establish timeout thresholds per phase (${timeout_seconds:300}s default)
Plan graceful degradation for partial failures

Data Flow

Document data transformations between stages
Specify data formats and validation rules
Plan for data persistence at checkpoints
Handle data cleanup after completion

Coordination Strategies

Communication Patterns

Direct: Agent-to-agent for tight coupling
Broadcast: One-to-many for status updates
Queue-based: Asynchronous for decoupled tasks
Event-driven: Reactive to state changes

Synchronization

Define sync points for dependent tasks
Implement waiting mechanisms with timeouts (${timeout_seconds:300}s)
Handle out-of-order completion gracefully
Maintain consistent state across agents

Conflict Resolution

Establish priority rules for resource contention
Define arbitration mechanisms for conflicts
Document rollback procedures for deadlocks
Prevent conflicts through careful scheduling

Performance Optimization

Load Balancing

Distribute work based on agent capacity
Monitor utilization and rebalance dynamically
Avoid overloading high-performing agents
Consider agent locality for data-intensive tasks

Bottleneck Management

Identify slow stages through monitoring
Add capacity to constrained resources
Restructure workflows to reduce dependencies
Cache intermediate results where beneficial

Resource Efficiency

Pool shared resources across agents
Release resources promptly after use
Batch similar operations to reduce overhead
Monitor and alert on resource waste

Monitoring and Adaptation

Progress Tracking

Monitor completion status per task
Track time spent versus estimates
Identify tasks at risk of delay
Report aggregated progress to stakeholders

Performance Metrics

Task completion rate and latency
Agent utilization and throughput
Error rates and recovery times
Resource consumption and cost

Dynamic Adjustment

Reallocate agents based on progress
Adjust priorities based on blockers
Scale team size based on workload
Modify workflow based on learning

Error Handling

Failure Detection

Monitor for task failures and timeouts (${timeout_seconds:300}s threshold)
Detect agent unavailability promptly
Identify cascade failure patterns
Alert on anomalous behavior

Recovery Procedures

Retry transient failures with backoff (up to ${retry_count:3} attempts)
Failover to backup agents when needed
Rollback to last checkpoint on critical failure
Escalate unrecoverable issues

Prevention

Validate inputs before execution
Test agent availability before assignment
Design for graceful degradation
Build redundancy into critical paths

Quality Assurance

Validation Gates

Verify outputs at each checkpoint
Cross-check results from parallel tasks
Validate final aggregated results
Confirm success criteria are met

Performance Standards

Agent selection accuracy target: >${agent_selection_accuracy:95}%
Task completion rate target: >${task_completion_rate:99}%
Response time target: <${response_time_threshold:5} seconds
Resource utilization: optimal range ${utilization_min:60}-${utilization_max:80}%

Best Practices

Planning

Invest time in thorough task analysis
Document assumptions and constraints
Plan for failure scenarios upfront
Define clear success metrics

Execution

Start with minimal viable team (${agent_count:3} agents)
Scale based on observed needs
Maintain clear communication channels
Track progress against milestones

Learning

Capture performance data for analysis
Identify patterns in successes and failures
Refine selection and coordination strategies
Share learnings across future orchestrations