multi-agent-orchestration

Coordinate multiple AI agents for complex tasks — decomposition, delegation, and synthesis

Zur Installation springen

Repository: fabioc-aloha/ChessCoach
Letzte Quellaktivität: 5. Mai 2026 um 20:58
Erkannte Sprache von SKILL.md: Englisch
Sterne: 1
Forks: 0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Zurück zur Suche Zurück zur Installation

type	skill
lifecycle	stable
inheritance	inheritable
name	multi-agent-orchestration
description	Coordinate multiple AI agents for complex tasks — decomposition, delegation, and synthesis
tier	standard
user-invokable	false
applyTo	*/agent,/orchestrat,/multi,/workflow,/subagent*
currency	2026-04-22T00:00:00.000Z

Multi-Agent Orchestration Skill

Decompose complex problems into agent-appropriate subtasks, delegate effectively, and synthesize results.

⚠️ Rapid Evolution Domain

Multi-agent patterns are evolving rapidly. This skill captures stable patterns while acknowledging the field is in flux.

Refresh triggers:

New orchestration frameworks (LangGraph, AutoGen, CrewAI releases)
Claude/GPT native multi-agent features
VS Code Copilot agent architecture changes

Last validated: February 2026

Core Concepts

When to Use Multi-Agent

Scenario	Single Agent	Multi-Agent
Simple code edit	✅	❌ Overkill
Multi-file refactor	✅ (if capable model)	⚠️ Consider
Research + implement	⚠️ Long context	✅ Decompose
Cross-domain task	❌ Context overload	✅ Specialists
Parallel independent work	❌ Sequential	✅ Parallel agents

Agent Roles

Role	Responsibility	Example
Orchestrator	Decompose, delegate, synthesize	Main chat session
Specialist	Deep expertise in one domain	Security reviewer agent
Worker	Execute well-defined subtask	"Find all usages of X"
Critic	Validate, review, improve	Code review agent

Decomposition Patterns

1. Horizontal Decomposition (Parallel)

Split task into independent subtasks that can run simultaneously.

┌─────────────────┐
│  Orchestrator   │
└───────┬─────────┘
        │ decompose
   ┌────┴────┬────────┐
   ▼         ▼        ▼
┌─────┐  ┌─────┐  ┌─────┐
│ A1  │  │ A2  │  │ A3  │   (parallel)
└──┬──┘  └──┬──┘  └──┬──┘
   └────────┼────────┘
            ▼
      synthesize

When to use:

┌─────────────────┐
│  Orchestrator   │
└───────┬─────────┘
        ▼
    ┌───────┐
    │  A1   │ → research
    └───┬───┘
        ▼
    ┌───────┐
    │  A2   │ → analyze
    └───┬───┘
        ▼
    ┌───────┐
    │  A3   │ → implement
    └───────┘

┌─────────────────┐
│   Root Orch     │
└───────┬─────────┘
   ┌────┴────┐
   ▼         ▼
┌─────┐   ┌─────┐
│SubO1│   │SubO2│    (sub-orchestrators)
└──┬──┘   └──┬──┘
 ┌─┴─┐    ┌──┴──┐
 ▼   ▼    ▼     ▼
┌─┐ ┌─┐  ┌─┐   ┌─┐
│W│ │W│  │W│   │W│   (workers)
└─┘ └─┘  └─┘   └─┘

Element	Purpose	Example
Context	What they need to know	"Working on Alex VS Code extension"
Scope	Clear boundaries	"Only look in /src/services"
Output	Expected format	"Return JSON with findings"
Constraints	What NOT to do	"Don't modify files, only report"

**Task:** [One-sentence objective]

**Context:**
- Project: [name/type]
- Relevant files: [list]
- What's already done: [state]

**Scope:**
- DO: [specific actions]
- DON'T: [boundaries]

**Expected Output:**
[Format and content expectations]

**Success Criteria:**
[How you'll know it's done right]

Pattern	When	How
Concatenate	Independent results	Simple append
Deduplicate	Overlapping searches	Hash/compare
Vote	Multiple opinions	Majority wins
Synthesize	Diverse perspectives	LLM summary
Validate	Critical decisions	Critic agent reviews

// Good: Clear task with expected output
await runSubagent({
  prompt: `Search the codebase for all error handling patterns.
           Return a JSON array of: {file, line, pattern, quality}`,
  description: "Find error patterns"
user-invokable: false
});

// Bad: Vague delegation
await runSubagent({
  prompt: "Look for problems in the code",  // Too vague
  description: "Find issues"
user-invokable: false
});

Scenario	Approach
Simple search	Direct `grep_search`
Complex multi-step search	`runSubagent`
Single file edit	Direct `replace_string_in_file`
Multi-file coordinated change	Consider subagent for planning
Research + implementation	Subagent for research, direct for implementation

Framework	Strength	Use Case
LangGraph	State machines, cycles	Complex workflows
AutoGen	Conversation patterns	Research, debate
CrewAI	Role-based teams	Business processes
VS Code Agents	IDE integration	Code tasks
Semantic Kernel	.NET native	Enterprise C#

Master Alex (orchestrator)
├── VS Code Heir → code analysis
├── M365 Heir → document synthesis
└── Global Knowledge → pattern matching