| How to choose between a reasoning agent and a FLOW-based agent | You need to decide whether an agent should be goal-driven and flexible, step-driven and predictable, or a mix of both. |
| How to decide whether to build one agent or multiple specialist agents | One customer-facing experience could be one broad agent or a supervisor with specialists. |
| How to design a supervisor that routes users to specialist agents | One entry point must identify what the user needs, choose a specialist, and pass enough context. |
| How to define clear responsibilities for each enterprise agent | An agent is becoming too broad or too vague for builders and support teams to reason about. |
| How to combine reasoning steps with deterministic FLOW steps | A conversation needs both flexible judgment and predictable execution. |
| How to write effective agent goals, personas, instructions, and limitations | An agent needs a clear job boundary, a consistent voice, and explicit limits. |
| How to use behavior profiles to change agent behavior by context | The same agent keeps its core responsibility but must change style, constraints, or tools by context. |
| How to configure model, timeout, and execution settings for an agent | An agent needs explicit model choice, response limits, timeout boundaries, or history windowing. |
| How to design reusable agents and modules for large projects | Many agents, tools, and workflows must compose without duplicated responsibilities or routing ambiguity. |
| How to use EXECUTION.pipeline for agent routing, classification, and short-circuiting | A supervisor needs classifier-assisted routing before the normal reasoning path decides what to do. |
| How to configure EXECUTION.pipeline models, modes, thresholds, and fallbacks | The execution pipeline exists but needs tuning for model, mode, confidence thresholds, or fallback behavior. |
