complexity-router

Complexity-based task routing classifies tasks as Small, Medium, or Large, then directs them to specialized agents. This orchestration model uses fresh context per phase to prevent context leakage and ensure clear handoffs across execution stages.

You route feature requests by describing the new task to the router, which assesses complexity upfront and initiates phase-based routing. The system assigns specialized agents to each phase, applying per-phase context resets to maintain clean execution boundaries.

Yes, phase-based orchestration supports bug reports and refactor scenarios alongside new features. The router evaluates the complexity of these tasks and coordinates agents across stages with clear handoffs and fresh context per phase.

The best way to prevent context leakage is applying per-phase context resets during agent orchestration. By resetting context for each phase, agents process their assigned stage independently without interference from prior phase data.

You need upfront complexity assessment when handling new tasks, feature requests, or bug reports that require phased execution. Assessing task complexity as Small, Medium, or Large beforehand determines the routing rules and agent coordination strategy.

Task execution loses track of earlier phases due to context limits in continuous orchestration. Implementing a phase-based model with fresh context per phase prevents this context leakage by isolating each stage's execution environment.