agent-run-orchestrator

mvillmow's avatarfrom mvillmow

Run section orchestrators to coordinate multi-component workflows. Use when starting work on a section.

⭐8stars🔀4forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The agent-run-orchestrator skill enables Claude to manage and execute complex, multi-component development workflows through hierarchical coordination. By invoking section-level orchestrators, it streamlines the transition from high-level planning to granular implementation, ensuring that tasks are efficiently decomposed, delegated to specialized agents, and monitored for progress across different architectural layers.

Use Cases

  • Initiating New Project Sections: Automatically break down high-level section specifications into manageable modules and delegate them to specialized design agents when starting a new phase of development.
  • Hierarchical Task Coordination: Manage the flow of information and task assignments from L1 Section Orchestrators down to L4 Implementation Engineers, ensuring architectural alignment at every level.
  • Parallel Workflow Management: Coordinate multiple simultaneous workstreams, such as foundation building, CI/CD setup, and shared library development, while maintaining a centralized view of progress and blockers.
  • Automated Progress Monitoring: Track the status of delegated tasks across the agent hierarchy and trigger escalation protocols when blocking issues are detected in the implementation pipeline.
nameagent-run-orchestrator
description"Run section orchestrators to coordinate multi-component workflows. Use when starting work on a section."
mcp_fallbacknone
categoryagent
user-invocablefalse

Run Orchestrator

Invoke section orchestrators to coordinate complex development workflows.

When to Use

  • Starting work on new section
  • Coordinating multiple parallel components
  • Managing complex workflows
  • Need hierarchical task coordination

Quick Reference

# Run orchestrator for section
./scripts/run_orchestrator.sh foundation

# Monitor section progress
./scripts/monitor_section_progress.sh

Orchestrator Workflow

  1. Review Plans - Understand section specifications
  2. Break Down - Divide into manageable components
  3. Delegate - Assign to appropriate design/specialist agents
  4. Monitor - Track progress and blockers
  5. Integrate - Coordinate results
  6. Escalate - Handle blocking issues

Hierarchy

Section Orchestrator (L1)
  ↓ delegates to
Module Design Agent (L2)
  ↓ delegates to
Component Specialist (L3)
  ↓ delegates to
Implementation Engineer (L4)

Orchestrator Levels

L0: Chief Architect - Strategic architecture decisions

L1: Section Orchestrators

  • Foundation Orchestrator
  • Shared Library Orchestrator
  • Tooling Orchestrator
  • Paper Implementation Orchestrator
  • CI/CD Orchestrator
  • Agentic Workflows Orchestrator

L2: Module Design Agents - Coordinate modules within sections

Agent Hierarchy Context

Orchestrators are the coordination hub between high-level planning and implementation teams. They decompose work from section level to component level, enabling parallel development.

References

  • /agents/hierarchy.md - Complete orchestrator structure
  • /agents/delegation-rules.md - Coordination patterns
  • .claude/agents/ - Orchestrator configurations