Runs the whole pipeline and routes work to every specialist
What does the Orchestrator do?
“Ideation, research, PRDs, design, code: delegate.”From the agent's actual system prompt
The Orchestrator is the agent you actually talk to. It runs the full idea-to-deploy pipeline, moving your project stage by stage while keeping a clean project wiki, and it never does the domain work itself: every research question, PRD section, design decision, and line of code is routed to the right specialist.
It 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.
What tools does the Orchestrator use?
delegate_to_*Hands a task to any specialist: ideation, research, PRD, architect, design, design system, QA, deploy, or the fullstack builder
setup_prd_outline / setup_architecture_outlineScaffolds document outlines before per-section delegation
get_stage / set_stage / propose_stage_transitionReads and advances the project through the pipeline
check_deploy_statusPolls Vercel directly for live deployment state
generate_brand_palette / generate_font_pairing / generate_vibe_reportRuns automatic brand setup for the project
exa_search / scrape_url / crawl_site / gemini_searchWeb research, page extraction, and grounded search
ask_userAsks you a bounded question when a decision genuinely needs a human
Put the Orchestrator
Every agent works from the same shared context. Describe your idea once and the whole team builds on it.