Your agentic dev team
Developer Team
A standing team of specialists — reviewers, builders, testers, researchers — that works a repository the way a real team does: a review pipeline with scopes, a build loop that ships increments, a harness that tests the team itself, and a learning loop that feeds what it finds back in.
What it does
The Developer Team runs on your repository from the command line. Ask it for a review and a coalition of specialists reads the whole branch against the scopes you chose, argues its findings through an arbitrator, and hands back a report you can act on. Ask it to build and the same team plans, implements, and verifies an increment at a time.
Key points
- 23 review specialists covering 187 lenses, plus 18 build lanes for the build loop.
- One of nine teams in the registry — 47 specialists between them.
- 19 review scopes — pick risk, completeness, or the whole set.
- A build loop that plans, implements, and verifies one increment at a time.
- A test harness that runs the team against fixtures and scores it.
- A learning loop that turns each run's findings into the next run's instructions.
- Memory that carries what the team learned between runs.
How far along it is
Developer preview. The review pipeline, the build loop, and the team registry are in daily use against this codebase; the test harness, the learning loop, and memory are real but still moving. The site marks each capability as live, in preview, or coming — nothing is claimed as finished that isn't.