Skip to main content
The Orchestrator runs the whole pipeline and routes work to every specialist. It is the agent you actually talk to: it moves your project stage by stage while keeping a clean project wiki, and it never does the domain work itself. Its own system prompt puts it bluntly: “Ideation, research, PRDs, design, code: delegate.” Every research question, PRD section, design decision, and line of code is routed to the right specialist. The Orchestrator is the only path between stages and the connective tissue of the whole system: it scaffolds outlines before delegating sections, proposes stage transitions for your approval, runs brand setup in automatic mode, and reads memory across every agent so nothing agreed in one stage gets forgotten in the next.

​
Tools

​
What it reads and produces

Reads: your idea, requests, and attachments; the full project wiki; cross-stage memory from every agent. Produces: stage transitions across the pipeline; a rolling progress ledger; a clean, current project wiki.

​
Where it sits in the pipeline

The Orchestrator is not a stage; it spans all of them. It is active from your first message in Ideate through the moment the Deploy Agent ships your product, and it is the only agent that talks to you at any point. The first specialist it typically delegates to is the Ideation Agent. Stage transitions are never silent. When the Orchestrator believes a stage is done, it proposes the transition and waits for your approval before moving on.
Talk to the Orchestrator in terms of outcomes, not agents. You do not need to name a specialist; say what you want (“compare the top three competitors’ pricing”, “add a settings page”) and the Orchestrator routes it. If you do want a specific agent involved, asking for it works too: delegation is its entire job.