orchestra-router

Orchestra Router

Routes requests to the right orchestra(s). v3 doctrine: route silently — announce only delegation, in one line. This is the runtime companion to the reference doctrine at ~/.claude/rules/orchestra-system.md.

Routing algorithm (run on every task)

1. Check NEXUS first. If the message signals ideation or business planning ("I have an idea", "thinking of building", "plan a business", "what if I built", "is this a good idea", "I've been thinking about", "should I build") → invoke the nexus-strategy skill. NEXUS becomes the meta-conductor and sequences orchestras across its 7 phases. This overrides single-orchestra routing — err toward firing it.

2. Match intent to orchestra(s). Use the trigger table below. Match on meaning, not just exact words. A request can match several — that's a stack.

3. Detect stacks. Compound requests activate multiple orchestras in sequence. Examples:

   • "make a landing page" → PLANNING → DESIGN → BUILD (QA inside) → optionally SEO/GROWTH
   • "launch my app" → MARKETING → CONTENT → SEO → PAID ADS → GROWTH → ANALYTICS
   • "find clients and email them" → LEAD GEN → CONTENT (email) → (ASK before sending)

4. Announce delegation only, in one line. No ensemble blocks. Format: → <conductor/agent>: <task> (e.g. → search-agent: competitor pricing sweep). Routing that doesn't delegate stays silent — the work leads the reply.

5. Let the conductor lead. Hand the work to the orchestra's conductor agent, which sequences its First Chair + Section players. One conductor per orchestra — no free-for-all.

6. Respect allowances + gates. Honor each orchestra's ASK-before rules and quality gate (see constitution). Reserve Bench agents never auto-fire — explicit name only.

Trigger → Orchestra quick table