Skip to main content
ProductOS is built around a team of specialized AI agents. You describe your idea once; the team researches it, writes the PRD, designs it, codes it, and deploys it. Each agent is narrow on purpose: it has its own system prompt, its own tools, and one job it does well.

The roster

Orchestrator

Runs the whole pipeline and routes work to every specialist. The only agent you talk to directly.

Ideation Agent

A Socratic thinking partner that sharpens your raw idea into a testable concept.

Research Agent

A market and feasibility investigator that grounds every claim in a source you can click.

PRD Agent

A requirements writer that works section by section, grounded in your research.

Architect Agent

An optional system design specialist for the technical half of Define.

Design Agent

A UI/UX specialist for brand, user flows, and screen specifications.

Design System Agent

A senior visual designer for tokens, components, and real HTML previews.

Fullstack Builder

The implementation agent that writes your actual codebase inside a live sandbox.

QA Agent

A real-browser tester that verifies the app actually works, ending in a single verdict.

Deploy Agent

Owner of the publish pipeline, from sandbox to a live URL you own.

Pipeline order

Agents map to the project stages you move through in Build: QA and Deploy are not stages. You run them as on-demand actions: QA whenever you want the app verified, Deploy whenever you want to ship.

One shared context

The agents do not start from scratch at each stage. Every agent reads the artifacts the previous agents produced, and the Orchestrator maintains a project wiki and cross-agent memory so nothing agreed in one stage gets forgotten in the next. Concretely, the chain of custody looks like this: the Ideation Agent logs assumptions and open questions; the Research Agent answers them with cited findings; the PRD Agent writes requirements against those artifacts rather than inventing them; the Design and Design System Agents design the product the PRD defines; the Fullstack Builder implements it on the exact design tokens the Design System Agent locked; the QA Agent tests the critical flows listed in the PRD.
You never address a specialist directly. The Orchestrator is the only agent that talks to you; it delegates every research question, PRD section, design decision, and line of code to the right specialist and proposes stage transitions for your approval.

Model configurability

No agent is hardcoded to a specific model. The model each agent runs on is admin-configurable, and you can bring your own keys instead of using platform credits: Anthropic, OpenAI, or Google keys, or an OpenRouter gateway key. See BYOK and models.

Where to go next

Start with the Orchestrator to understand how work gets routed, then follow the pipeline in order from Ideation through Deploy. If you want the stage-by-stage product walkthrough instead of the agent-by-agent view, see the Build surface overview.