assist

You can route user requests by using an intent-driven orchestrator that detects the task type and selects the correct operation from a routing matrix. This centralizes decision-making and eliminates command sprawl for zaileys tasks.

Intent-based routing is a mechanism that analyzes a user's request to automatically select the appropriate action, such as scaffolding or debugging. It uses a routing matrix to map detected intents to specific capabilities, streamlining the workflow.

Yes, you can use a single orchestrator entry point to manage multiple operations like migrate and review. It hides the complexity of separate commands by routing each request to the correct capability based on detected intent.

The best way to ensure consistent guidance is to use reference-grounded decisions. The orchestrator uses prepared deep references and recipes to verify actions, ensuring that the selected scaffold, debug, or explain tasks are accurate.

Yes, you need prepared deep references to ground routing decisions. These references provide the necessary context for the orchestrator to accurately detect intents and select the correct code generation or debugging operations.

Intent routing reduces command sprawl by centralizing decision-making into a single entry point. Instead of manually selecting from multiple commands, the orchestrator automatically detects the task intent and directs the request to the proper capability.