factory-orchestrator

Orchestrate expert agents across domains using structured routing patterns.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/m16khb/claude-integration --skill factory-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-orchestrator
Source: https://github.com/m16khb/claude-integration/tree/main/plugins/automation-tools/skills/factory-orchestrator
Command: npx skills add https://github.com/m16khb/claude-integration --skill factory-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates orchestrators that compose multiple expert agents to tackle complex, multi-domain tasks.

Core Features & Use Cases

  • Orchestration strategies: SINGLE_EXPERT, SEQUENTIAL_CHAIN, PARALLEL_EXECUTION, HIERARCHICAL_DELEGATION, DYNAMIC_ROUTING.
  • Expert classification & routing: Classifies specialists by domain and maps tasks to appropriate agents.
  • Delegation examples: Patterns for task handoffs and context transfer.
  • Usage Scenario: Combine a code-reviewer and a testing-expert to perform sequential validation of a feature.

Quick Start

Define an Input with a Selected experts list and a desired pattern, then generate the orchestration plan.

Frequently Asked Questions about factory-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multiple expert agents to handle complex tasks across different domains?

Multi-agent orchestration routes tasks to specialized agents based on domain and context. This skill provides five orchestration patterns—SINGLE_EXPERT, SEQUENTIAL_CHAIN, PARALLEL_EXECUTION, HIERARCHICAL_DELEGATION, and DYNAMIC_ROUTING—to coordinate experts across backend, frontend, DevOps, testing, and documentation work, ensuring each task reaches the right specialist.

What orchestration patterns work best for sequential task delegation between multiple agents?

Sequential orchestration chains agents in order, passing outputs from one expert to the next. For example, route code to a reviewer first, then pass approved changes to a testing expert. This pattern enforces workflow-driven execution where each agent completes before the next begins.

Can I run agent tasks in parallel instead of sequentially?

Yes, parallel execution runs multiple agents simultaneously on independent subtasks. This orchestration pattern reduces latency when agents work on separate concerns—such as frontend validation and backend integration testing—then aggregates results before proceeding.

How do I route tasks to the right expert agent based on task content?

Keyword- and context-based routing classifies incoming tasks by domain and automatically maps them to appropriate specialists. This dynamic routing pattern identifies whether a task belongs to backend development, frontend work, infrastructure, testing, or documentation and delegates accordingly.

What's the difference between hierarchical delegation and flat parallel execution?

Hierarchical delegation creates supervisor-subordinate relationships where higher-level agents direct subtasks to specialized workers in a tree structure. Parallel execution treats agents as equals, running them simultaneously without dependency chains. Hierarchical works for complex dependencies; parallel suits independent workloads.

Do I need to specify expert agents upfront or can the orchestrator discover them dynamically?

You define a selected experts list and desired pattern as input; the orchestrator generates a coordination plan mapping tasks to those agents. The dynamic routing pattern can select among available experts at runtime based on task content, while other patterns use your predefined expert assignments.