ultrathink-orchestrator

Workflow routing automatically detects whether your request is a development or investigation task, estimates complexity, and invokes the appropriate workflow after you confirm. Simply describe what you need—like 'implement authentication'—and the orchestrator handles task-type detection and workflow selection.

Development workflows handle feature implementation and code changes; investigation workflows handle troubleshooting, debugging, and analysis tasks. The orchestrator detects keywords in your request to classify the task type and route to investigation-workflow or default-workflow accordingly.

Yes. The orchestrator falls back to markdown workflow definitions when skills are unavailable, ensuring task routing continues without requiring all skills to be installed. You still get automatic detection and routing with fallback execution.

The orchestrator estimates complexity based on task keywords and scope detected in your request. This estimation informs which workflow variant to invoke, helping match the right process depth to your actual task needs before execution begins.

No. The orchestrator automatically selects the workflow based on task-type detection; you only confirm before proceeding. Manual workflow selection is eliminated, reducing friction in repetitive development and investigation work.

Keywords like 'investigate,' 'debug,' 'develop,' 'implement,' 'fix,' and 'analyze' trigger detection. Hybrid requests containing both development and investigation keywords are also detected and routed to the appropriate combined workflow.