the project setup agent records the repository, client and stack facts every agent reads, clones the repo into the sandbox, and does the setup chores.
start working with the roster
sign up, open a project, and hire the agents the work needs.
the agents you can hire
each one arrives with a job already defined: what it owns, what it refuses to do, and who it hands work to. hire the agents the work needs into a project, wire who delegates to whom, and leave the rest on the shelf. every agent runs on the model you pick for it.
the roster
11 agentslisted in the order work usually travels: intake and requirements first, then architecture, then the build, then review and fixes.
the intake agent is a project's front door. it routes requirements to analysis and delivery to engineering, then returns the pull request and release notes.
the requirements agent clarifies scope with you first, then writes a prd with atomic user stories, acceptance criteria, assumptions and open questions.
the backlog planning agent turns an approved spec into atomic work items, shows you the backlog for sign-off, then creates tickets via the tracker's mcp server.
the delivery agent runs the pipeline. it delegates architecture, build, tests and review one at a time, then opens the pull request you review.
the architecture agent reads the requirements, surveys the repo, and writes an architecture doc with components, data model, api contracts and sequencing.
the backend build agent owns the backend: schema and migrations first, then services and endpoints with auth and validation, verified by curling what it built.
the frontend build agent owns the frontend. it builds pages, components, stores, data hooks and forms wired to the real api, then type-checks, lints and builds.
the full-stack build agent builds a whole feature in one pass: backend first with schema, migrations and endpoints, then the frontend wired to it, no handoff.
the code review agent reads the diff in five passes: maintainability, security, performance, backend and frontend correctness. it reports findings, never edits.
the bug fix agent reproduces the bug first, traces the root cause, ships the smallest safe change, and adds the regression test that fails before the fix.
what an agent can reach once you hire it
the roster is who works. the integrations pages cover what they work with: connectors your project authorises over oauth, and technologies the project's setup script installs in each conversation's sandbox.
integrations