consult

To get expert advice without multi-agent panel overhead, you route your specific question into a single-agent consult mode. This dispatches a direct-answer output shape to the appropriate consult-capable subagent, preserving your question context.

Single-agent consultation provides focused guidance from one expert perspective. You should use it when your question has one dominant lens and you want direct advice rather than broad panel synthesis, code review, or spec critique.

You route your request by explicitly selecting or inferring the target subagent role. The system matches your question to the most relevant lens, such as systems, Rust, product strategy, or security, and dispatches it to that specific consult-capable roster.

No, single-agent consultation does not require explicit agent selection. The system accepts explicit selection but can also infer the appropriate consult-capable subagent based on the context of your submitted question.

The best way to reduce token use is to request single-expert consultation instead of a broad multi-agent review. This avoids panel overhead and returns direct expert advice, keeping token consumption low while providing high-signal guidance.

You use single-agent consultation because it avoids panel overhead and returns direct expert advice. It is designed for scenarios where your question has one dominant lens, ensuring you receive focused, high-signal guidance without unnecessary token consumption.