跳到正文
cccskills
免费在 GitHub 公开

agent-orchestrator-task

Breaks complex goals into actionable tasks, plans their order, and coordinates execution across agents. It tracks progress, adjusts priorities and dependencies, and combines separate outputs into a consistent deliverable.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

查看安装方法

适用场景

  • Coordinate development of a multi-part authentication system
  • Manage payment module work from analysis through testing
  • Run tests and documentation updates in parallel
  • Integrate changes from multiple refactoring agents

包含的文件(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。


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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

中文简介正在准备中。当前显示英语简介。

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7万2026年10月18日 更新

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

中文简介正在准备中。当前显示英语简介。

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7万2026年10月18日 更新

adr-index

免费

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

中文简介正在准备中。当前显示英语简介。

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7万2026年10月18日 更新

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

中文简介正在准备中。当前显示英语简介。

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7万2026年10月18日 更新

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

中文简介正在准备中。当前显示英语简介。

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7万2026年10月18日 更新

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

中文简介正在准备中。当前显示英语简介。

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7万2026年10月18日 更新

查看 ruvnet 的全部技能

报告此技能的问题