The Team
A team, not a tool. Working together. Under your control.
How it's structured
Portfolio to PR, One Chain of Custody
Every role has a boundary. No single agent holds both the pen and the merge button.
Portfolio Claudia
Portfolio agentCoordinates across every repo you own
Sequences work and resolves conflicts across your whole portfolio — inside the direction you've already approved.
- Cross-repo sequencing and dependency awareness
- Routes work descriptions to the right repository
- Escalates direction changes to you, never decides them alone
Resident Repo Agent
Per-repo agentLives in a single repo, keeps the backlog honest
Grooms and revalidates the backlog just-in-time, schedules native the schedule work, and merges reviewed work when policy allows.
- Just-in-time issue revalidation against the current default branch
- Applies the effective autonomy threshold before scheduling work
- Squash-merges a reviewed, current-head, green PR and confirms closure
Builder
Merge-denied implementerClaude Code, Codex, or Cursor — never the merge button
Implements one issue at a time with TDD, in an isolated git worktree, using whichever vendor fits the work.
- Writes failing tests from acceptance criteria, then implements
- Runs validation — test, lint, typecheck, build — before opening a PR
- Value-based routing: frontier models on frontier work, efficient models on routine work
Independent Reviewer
Cross-vendor gateA different vendor than the one that built it
Reviews every PR in one independent conversation — quality, security, and correctness — with the conclusion recorded on the PR.
- Reviewer runs on a vendor different from the builder, where available
- One conversation, one final conclusion — no review rounds
- Findings are resolved in that same conversation before merge
The key boundary
Implementation and merge never share an agent
Builders write the code. A different-vendor reviewer checks it. The resident repo agent merges it. Each role is real and enforced, not a suggestion in a prompt.
0
Builder Merge Rights
GitHub merge commands are denied to builder profiles by native policy.
1
Review Conversation
One independent, cross-vendor review — findings resolved, conclusion recorded on the PR.
100%
Traced to an Issue
Every change starts as a GitHub issue and ends as a reviewed, merged PR.
The Team Runs Skills
Skills are the user-facing commands; the team above is who's actually behind them. See the full lifecycle catalog on Capabilities.
Ready to Try Claudia?
A team, not a tool. Working together. Under your control.