Bring a guide for the hard stretches.
Every trail has its own terrain. Give your party a reviewer, a QA lead, a security expert or a docs writer. Any agent that picks up their tickets works to their role, and Scout makes sure the checklist gets done.
A general-purpose agent is a generalist. Your trail isn't.
The same agent that writes the code shouldn't be the one that signs it off, and a security pass needs a different eye than a docs pass. Guides give each kind of work its own instructions and its own bar.
Pick them, add them to the party, and they work to the checklist.
-
01
Pick a guide
Browse a moderated catalog of roles, or write your own. Each one is a short file: instructions, a checklist and the checks it needs.
-
02
Add them to the trail
Tickets say which role they need, and the trail lists its party. Scout routes each ticket to an agent that can take it.
-
03
They work to their checklist
The agent that claims the ticket gets the role's instructions and checklist, and can't finish until every item is answered.
Five built-in roles, and room for yours.
The reviewer builds on the independent review Teamtrail already runs today: a different agent checks every change before it counts as done. The others follow the same pattern.
- ReviewerChecks the change against what was claimed, with findings and a verdict
- QATries the edges and failure paths before it ships
- SecurityReads the change the way an attacker would
- DocsKeeps docs and examples true to the code
- ArchitectGuards boundaries and the shape of the system
- + CommunityRoles from the catalog, or one you write for your team
A guide can raise the bar. Never lower it.
Bringing someone in from a catalog has to be safe by default. These rules are enforced by Teamtrail, not by the role.
-
No code in a role
Roles are instructions and checklists. No scripts, no hooks, nothing that runs on install.
-
You approve every check
A command a role proposes runs only after you approve it, and it goes into your repo's config.
-
Pinned and verified
Each installed role is pinned to a version and fingerprint. A file that changes is switched off until you look.
-
Roles only add rules
A role can add checks and checklist items. It can't skip review, lower verification or decide for you.
Guides aren't tied to a model.
A role is plain text that travels with the ticket. Claude Code, Codex or any agent that connects over MCP picks it up when it claims the work. No vendor lock-in, no hosted agents, and still all on your machine.
Be first to bring a guide.
We'll email you once, when the marketplace opens. Until then, Teamtrail and its built-in review work today.