Orchestrators

Orchestrators coordinate multiple agents to handle complex, multi-step tasks. Instead of invoking agents one by one, you invoke an orchestrator and it does the coordination for you.

The 7 orchestrators

graph TB
    subgraph "Development"
        CO[conceptual-orchestrator<br/>/plan]
        IO[implementation-orchestrator<br/>/review]
        DO[deployment-orchestrator<br/>/deploy-check]
        BO[bugfix-orchestrator<br/>/investigate-bug]
        IN[incident-orchestrator<br/>/incident-response]
    end
    subgraph "Product Design"
        PD[product-design-orchestrator<br/>/pd-0-start]
    end
    subgraph "Knowledge Work"
        KW[knowledge-work-orchestrator<br/>/kw-0-start]
    end

Orchestrator	Command	Purpose
conceptual-orchestrator	/plan	Research, architecture, specs
implementation-orchestrator	/review	Code review with 6 parallel reviewers
deployment-orchestrator	/deploy-check	Pre-deploy verification
bugfix-orchestrator	/investigate-bug	Bug investigation and root cause
incident-orchestrator	/incident-response	Production incident response
product-design-orchestrator	/pd-0-start	Product design workflow coordination
knowledge-work-orchestrator	/kw-0-start	Knowledge work workflow coordination

How orchestrators work

Every orchestrator follows the same pattern:

1. Understand — clarify the request
2. Load knowledge — consult past solutions and patterns (Step 0)
3. Plan — create a visible todo list
4. Dispatch — invoke sub-agents (parallel when possible)
5. Aggregate — combine results
6. Report — produce structured output
7. Handoff — guide to the next phase

Conceptual orchestrator

When to use: Starting new features, evaluating approaches, writing specs.

Dispatches:

• best-practices-researcher — industry patterns
• framework-docs-researcher — library documentation
• architecture-strategist — system design
• spec-flow-analyzer — user flow mapping

Output: Design specification, architecture decisions, implementation plan.

/plan "Add notification system for our B2B SaaS"

Implementation orchestrator

When to use: Reviewing code for quality and security.

Dispatches 6 reviewers in parallel:

• security-sentinel — security vulnerabilities
• kieran-typescript-reviewer — TypeScript quality
• julik-frontend-races-reviewer — race conditions
• code-simplicity-reviewer — complexity
• performance-oracle — performance issues
• pattern-recognition-specialist — code patterns

Output: Quality gate report with findings by severity.

/review

Deployment orchestrator

When to use: Before deploying to production.

Runs:

• Dependency security audit
• Final security scan
• Migration safety check
• Compliance verification (GDPR/SOC2)

Output: Go/No-Go decision with rollback plan.

/deploy-check

Bugfix orchestrator

When to use: Investigating bugs, especially recurring ones.

Dispatches:

• bug-reproduction-validator — reproduce the issue
• git-history-analyzer — historical context
• pattern-recognition-specialist — pattern detection

Output: Root cause analysis with fix recommendations.

/investigate-bug "Users can't export reports"

Incident orchestrator

When to use: Production incidents requiring immediate response.

Handles:

• Severity assessment
• Mitigation options (rollback, feature flag, hotfix)
• Post-mortem template
• Runbook generation

/incident-response

When NOT to use orchestrators

Skip orchestrators for:

• Single-file, obvious fixes
• Quick codebase questions
• Exploratory reading
• Tasks where you know exactly which agent to use

In those cases, invoke the agent directly:

"Use security-sentinel to check this function"
"Run kieran-typescript-reviewer on this file"