The team
Your AI dev team
Not one agent doing everything: a team of specialists, each with its own role and its own cloud machine. The spec writer plans, developers build, QA breaks things on purpose, the code reviewer reads every diff, and the product reviewer checks it against the job. You approve at the gates.
Plans the work
The Spec Writer
Turns your job into a spec and mockups, and breaks it into tasks.
Before any code is written, the spec writer turns your plain-English job into a spec: what gets built, what does not, and the open decisions you need to make. You approve the spec before anything moves, and changes come back to you the same way.
Write the code
The Developers
Implement the spec task by task, each on its own cloud machine.
Developer agents work through the plan task by task, each on a persistent cloud machine with VS Code, a terminal, Docker, and a real browser. They can run in parallel on independent tasks, and they commit their work as they go.
Tries to break it
The QA Agent
Writes and runs unit and browser tests against what the developers built.
QA is a separate agent, not a step the developer skips when it feels confident. It writes unit tests, and it runs browser E2E tests against the real app: clicking through flows the way a person would. Failures go back to the developers with reproduction steps.
Reviews the diff
The Code Reviewer
Reviews every change for correctness, security, and style before a human sees it.
The code reviewer reads the full diff against the spec: correctness, security issues, performance problems, and whether the change actually does what the spec said. Anything questionable comes back with specifics, not vibes.
Checks it against the job
The Product Reviewer
Verifies the feature works from the user point of view and matches the spec.
The product reviewer asks the question code review cannot: does this do what the customer actually asked for? It exercises the feature end to end and flags gaps between the spec, the implementation, and the intent.
Research, marketing, ops
Your Agents Beyond Code
The same machinery for work that is not code: research briefs, marketing plans, ops automation.
The specialist pattern is not limited to software. Marketing agents own goals like growing signups, research agents compile briefs, and ops agents watch schedules. Each runs on its own machine with its own memory that grows every session.
How they work together
Work moves through the team as a pipeline: spec, plan, build, QA, code review, product review, and each stage is a separate agent so the checks are real, not a checkbox. The guided build workflow walks through one feature end to end, and Focus is where their questions find you.
Want to see one in action? Meet the marketing agent, or start free and hand your first agent a job.