What problem does it solve?
Analyzes feature descriptions to determine the appropriate flow_mode (express, standard, or deep) and routes execution to the correct workflow agent, ensuring orchestration is driven by agent orchestration rather than by the skill name.
Core Features & Use Cases
- Maps flow_mode values to corresponding workflow agents: express → express-workflow, standard → standard-workflow, deep → deep-workflow, enabling end-to-end execution without duplicating skill identities.
- Treats routing as a pre-processing and state-management skill that decides when and which workflow agent to invoke, while the actual specification, design, and tasks are executed by the workflow agents.
- Leverages a complexity-analyzer for recommended flow_mode when not explicitly forced, while honoring explicit --workflow selections and safety constraints to avoid premature branching or state writes.
Quick Start
Provide the initial arguments; the routing system determines the flow_mode and dispatches to the matching workflow agent.