orchestratelisted

# Orchestrate — intelligent task routing ## Activation Invoked via /orchestrate. Run before any medium or large task. Auto-activates when a request is Tier 2 or Tier 3 per the routing rules in CLAUDE.md. Never auto-activates for Tier 1 tasks. ## Process ### Step 1 — Evaluate complexity Without reading any files, estimate the task tier: TIER 1 (handle in main session): - Under 20 min, 1-2 files, single concern → Skip orchestration. Proceed directly. TIER 2 (ask user): - 20-60 min, 3-8 files, 2-3 concerns → Continue to Step 2. TIER 3 (recommend sub-agents): - Over 60 min, 9+ files, 4+ concerns, parallel workstreams → Continue to Step 2 with a recommendation. ### Step 2 — Ask the user Use AskUserQuestion: AskUserQuestion({ questions: [ { question: "This looks like a [Tier 2/3] task. How should I approach it?", options: [ "Main session — handle everything here (simpler, no overhead)", "Sub-agents — dispatch to specialists (better for large tasks)", "Show me the plan first, then I'll decide" ] } ] }) If the user selects "Show me the plan first": - Outline the task breakdown: what sub-agents would handle what - Show estimated token cost (number of workers × task size) - Then ask again with the two remaining options ### Step 3 — If main session chosen Proceed using the existing /build or /engineer skill. No sub-agents. Keep it simple. ### Step 4 — If sub-agents chosen 4a. D