An orchestrator with exactly one job.
The Coordinator sequences an 11-stage conversation across eight child agents and three prompt tools — then classifies, dual-routes, and auto-submits. Hover any specialist to see its role and when it fires; Stage 1 is the skills-based replatform underway.
One orchestrator, eight specialists
A Copilot Studio multi-agent system: a single-responsibility orchestrator routes an 11-stage conversation to eight child agents (plus three prompt tools for clarifying vague input), then classifies the request and dual-routes it. On confirmation it writes the intake to SharePoint, generates a Word brief, and creates a Jira ticket. Hover or tap an agent to see its role.
Hover or tap an agent above to see its pipeline and what it returns for this bid.
◆Intake Orchestrator— Routes the conversation; stays behind the scenes
A single-responsibility orchestrator: it sequences an 11-stage conversation across eight specialists and three prompt tools, tracks session state in 20 variables, and confirms with the user before anything is submitted — but it makes no domain decision itself and stays behind the scenes. That single responsibility was the breakthrough: an earlier version tried to both coordinate and converse, and evals caught it.
Why it matters · One job — sequencing — done deterministically. Every decision is delegated to a specialist, which is exactly what makes the system debuggable and safe.