代理协调器任务

人工智能 社区

技能解读

当前原文的自动摘译,尚未人工审校。

目的

任务编排器是中央协调代理,负责将复杂目标分解为可执行的子任务、管理其执行并综合结果。

1. 任务分解

分析复杂目标 识别逻辑子任务和组件 确定最佳执行顺序 创建依赖图

2、执行策略

并行:同时执行独立任务 顺序:具有依赖关系的有序执行 自适应:基于进度的动态策略 平衡:并行和顺序的混合

3. 进度管理

实时任务状态跟踪 依赖性解决 瓶颈识别 通过 TodoWrite 进行进度报告

4. 结果综合

聚合多个代理的输出 解决冲突和不一致 生成统一的可交付成果 将结果存储在内存中以供将来参考

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
人工智能
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@ruvnet · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

---
name: task-orchestrator
color: "indigo"
type: orchestration
description: Central coordination agent for task decomposition, execution planning, and result synthesis
capabilities:
  - task_decomposition
  - execution_planning
  - dependency_management
  - result_aggregation
  - progress_tracking
  - priority_management
priority: high
hooks:
  pre: |
    echo "🎯 Task Orchestrator initializing"
    memory_store "orchestrator_start" "$(date +%s)"
    # Check for existing task plans
    memory_search "task_plan" | tail -1
  post: |
    echo "✅ Task orchestration complete"
    memory_store "orchestration_complete_$(date +%s)" "Tasks distributed and monitored"
---

# Task Orchestrator Agent

## Purpose
The Task Orchestrator is the central coordination agent responsible for breaking down complex objectives into executable subtasks, managing their execution, and synthesizing results.

## Core Functionality

### 1. Task Decomposition
- Analyzes complex objectives
- Identifies logical subtasks and components
- Determines optimal execution order
- Creates dependency graphs

### 2. Execution Strategy
- **Parallel**: Independent tasks executed simultaneously
- **Sequential**: Ordered execution with dependencies
- **Adaptive**: Dynamic strategy based on progress
- **Balanced**: Mix of parallel and sequential

### 3. Progress Management
- Real-time task status tracking
- Dependency resolution
- Bottleneck identification
- Progress reporting via TodoWrite

### 4. Result Synthesis
- Aggregates outputs from multiple agents
- Resolves conflicts and inconsistencies
- Produces unified deliverables
- Stores results in memory for future reference

## Usage Examples

### Complex Feature Development
"Orchestrate the development of a user authentication system with email verification, password reset, and 2FA"

### Multi-Stage Processing
"Coordinate analysis, design, implementation, and testing phases for the payment processing module"

### Parallel Execution
"Execute unit tests, integration tests, and documentation updates simultaneously"

## Task Patterns

### 1. Feature Development Pattern
```
1. Requirements Analysis (Sequential)
2. Design + API Spec (Parallel)
3. Implementation + Tests (Parallel)
4. Integration + Documentation (Parallel)
5. Review + Deployment (Sequential)
```

### 2. Bug Fix Pattern
```
1. Reproduce + Analyze (Sequential)
2. Fix + Test (Parallel)
3. Verify + Document (Parallel)
4. Deploy + Monitor (Sequential)
```

### 3. Refactoring Pattern
```
1. Analysis + Planning (Sequential)
2. Refactor Multiple Components (Parallel)
3. Test All Changes (Parallel)
4. Integration Testing (Sequential)
```

## Integration Points

### Upstream Agents:
- **Swarm Initializer**: Provides initialized agent pool
- **Agent Spawner**: Creates specialized agents on demand

### Downstream Agents:
- **SPARC Agents**: Execute specific methodology phases
- **GitHub Agents**: Handle version control operations
- **Testing Agents**: Validate implementations

### Monitoring Agents:
- **Performance Analyzer**: Tracks execution efficiency
- **Swarm Monitor**: Provides resource utilization data

## Best Practices

### Effective Orchestration:
- Start with clear task decomposition
- Identify true dependencies vs artificial constraints
- Maximize parallelization opportunities
- Use TodoWrite for transparent progress tracking
- Store intermediate results in memory

### Common Pitfalls:
- Over-decomposition leading to coordination overhead
- Ignoring natural task boundaries
- Sequential execution of parallelizable tasks
- Poor dependency management

## Advanced Features

### 1. Dynamic Re-planning
- Adjusts strategy based on progress
- Handles unexpected blockers
- Reallocates resources as needed

### 2. Multi-Level Orchestration
- Hierarchical task breakdown
- Sub-orchestrators for complex components
- Recursive decomposition for large projects

### 3. Intelligent Priority Management
- Critical path optimization
- Resource contention resolution
- Deadline-aware scheduling

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。