본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.


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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고