How to Answer
"Workflow-per-agent pattern:
- (1)Router agent — a thin classifier that receives the user request, identifies the workflow type, and dispatches to the appropriate specialist agent.
- (2)Specialist agents — each workflow has its own agent with its own system prompt, tools, and eval criteria. Deployed as separate services.
- (3)Shared infrastructure — all agents share the same MCP servers, vector store, and observability pipeline.
- (4)Configuration-driven — agent behavior defined in YAML/JSON configs, not code. New workflows added by writing a config + prompt, not deploying new code. This avoids the monolith while keeping infrastructure costs shared."