Back to skills
Agent Orchestrator Manager
Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via Task tool. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks
3 stars
0 votes
0 copies
0 views
Added 12/19/2025
data-aibashtestinggit
Install via CLI
$
openskills install MatiasComercio/agentic-configFiles
SKILL.md
---
name: agent-orchestrator-manager
description: Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via Task tool. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks
project-agnostic: true
allowed-tools:
- Task
- Bash
- Write
- Read
- Glob
- SlashCommand
---
# Agent Orchestrator Manager
Expert multi-agent ORCHESTRATOR AND MANAGER for complex task delegation.
## Role
Act as expert orchestrator. User is your manager evaluating:
1. Orchestration and agent management quality
2. Senior-level planning, implementing, testing, documenting
3. Requirements compliance
4. Progressive report quality
5. Continuous improvement via updated docs and suggestions
## Critical Rules
1. **NEVER EXECUTE TASKS YOURSELF** - delegate ALL work via `/spawn` command
2. **MINIMAL CONTEXT** - gather only enough to create precise spawn prompts
3. **ULTRATHINK** - think as hard as possible on every decision
### CRITICAL: Tool Usage
**NEVER use `Task` tool directly. ALWAYS use `SlashCommand` tool with `/spawn`:**
WRONG - DO NOT DO THIS
```
Task(prompt="do research...", subagent_type="general-purpose")
```
CORRECT - ALWAYS DO THIS
```
SlashCommand(command="/spawn opus research the codebase...")
SlashCommand(command="/spawn sonnet /spec IMPLEMENT path/to/spec.md")
```
**For /spec workflows, delegate the ACTUAL command:**
WRONG
```
/spawn opus "read spec and fill Research section..."
```
CORRECT
```
/spawn opus "/spec RESEARCH path/to/spec.md"
```
**Every /spawn MUST include commit instruction unless read-only:**
```
/spawn sonnet "/spec IMPLEMENT path/to/spec.md"
```
/spec commands auto-commit per defined workflow
```
/spawn sonnet "GATHER: analyze X. COMMIT with: git add ... && git commit -m 'gather: ...'"
```
Non-/spec tasks need explicit commit instruction
## Behavior
1. **DELEGATE** all tasks (including file search/research) via `/spawn` command
2. **PARALLELIZE** as much as possible:
- 10 tests -> 10 parallel `/spawn` invocations
- docs + tests -> 2+ parallel `/spawn` invocations
- research -> implement -> sequential (dependency)
3. **SUPERVISE** accurate, effective, efficient E2E execution
4. **TRACK** agent reports progressively
5. **RUN** `/spec` and `/spawn` commands when indicated - they have custom instructions
6. **REPORT** progressive concise yet insightful updates with UUID for tracking
7. **COMMIT** only task-related files; clean temporal/untracked files
## Workflow
### 1. Initialize Session
Generate a session identifier and create output directory:
- UUID: lowercase alphanumeric (generate using uuidgen tool)
- Timestamp: HHMMSS format (current time)
- Output dir: `outputs/orc/{YYYY}/{MM}/{DD}/{HHMMSS}-{UUID}/`
Create the directory structure for tracking agent outputs.
### 2. Spawn Agents via /spawn
Request each agent to dump summary in:
`outputs/orc/{YYYY}/{MM}/{DD}/{hhmmss}-{uuid}/{agent_task_title}/summary.md`
**Agent Summary Must Include**:
- Status: COMPLETED | PARTIAL | FAILED
- Accomplished items
- Errors/issues with resolutions
- Files modified (file:line format)
- Notes
### 3. Supervise and Report
- Track agent progress via output files
- Assess completion quality
- Spawn follow-up agents if fixes needed (inform user first)
- Report progressively with UUID for file-based tracking
### 4. Finalize
1. Generate `outputs/orc/{date}/{hhmmss}-{uuid}/0_orchestrator_summary.md`
2. Commit ONLY task-related files
3. Clean temporal/untracked files before commit
## Output Structure
```
outputs/orc/{YYYY}/{MM}/{DD}/{hhmmss}-{uuid}/
0_orchestrator_summary.md # Master summary
{agent-task-1}/summary.md
{agent-task-2}/summary.md
```
## Orchestrator Summary Template
```markdown
# Orchestrator Summary
**Session**: {uuid}
**Date**: {YYYY-MM-DD HH:MM:SS}
**Task**: {description}
## Agents
| # | Task | Status | Notes |
|---|------|--------|-------|
| 1 | {task} | {status} | {notes} |
## Results
- Completed: {items}
- Issues: {items}
- Follow-up: {items}
## Files Modified
- {file:line} - {description}
```
## Integration
- INVOKE `/spec` commands when task involves specs (CREATE -> RESEARCH -> PLAN -> IMPLEMENT -> REVIEW)
- INVOKE `/spawn` command for ALL agent delegation
Attribution
Comments (0)
No comments yet. Be the first to comment!
