bimaiYour team
Which agents are on your team, why they're there, and how to change it.
Not built yet
Roles
bimai has a catalogue of roles. Your team is a small selection from it, never all of them.
| Role | What it does for you |
|---|---|
| Coordinator | Runs the team, follows the project's workflows, talks to you. Always on the team. |
| Requirements & Risk Manager | Requirements, verification status, risks and mitigations. Needs a Relatics export or similar. |
| Planning Analyst | Milestones, critical path, slipping deliverables. Needs a Primavera or MS Project planning. |
| Information Manager | BEP and EIR compliance, naming, status codes, delivery readiness. |
| Model Checker | Queries models and checks them against the agreements. |
| Issue Manager | Triages, clusters and follows up issues. |
| Scribe | Minutes, reports and the decision log. |
| Mentor | Explains VS Code and what bimai does, if you're new to it. |
| Builder | Adds new tools to bimai. Only for people who build. |
How your team is chosen
A role only joins if it serves something you asked help with and the data it needs exists. No Relatics export and no interest in requirements means no Requirements & Risk Manager. A team has at most five members. Your team file records why each member is there:
| Member | Why |
|---|---|
| Coordinator | Always |
| Requirements & Risk Manager | Goals: requirements, risks · Data: Relatics export |
| Planning Analyst | Goal: planning · Data: Primavera XML |
| Scribe | Goals: meetings, design progress reporting |
Who handles what
Available
bimai team work today.The Coordinator follows a routing table that bimai writes into CLAUDE.md for your team. Each row
says what work a member handles, with two example requests:
| Work | Who | For example |
|---|---|---|
| Quick facts from the project files, and anything no team member covers | Coordinator | "who holds the structure position?" |
| Model contents, model checks and version comparisons | Model Checker | "which walls have no fire rating?" |
| Minutes, reports and recording decisions | Scribe | "here is the transcript of today's meeting" |
And a few rules: quick facts are answered directly, every task has exactly one member responsible (bimai tells you who), and work nobody on the team covers is done by the Coordinator, which says so.
What your team remembers
Every member keeps a history in .bimai/positions/<position>/agents/<role>/history.md. It belongs to
the position, not the person: when a colleague takes over the job, the agents still know what
they learned there.
Agents read their history before they start and add only confirmed, lasting things: conventions,
preferences, where things are. One dated line each, with where it came from. Never requests or
guesses, never personal remarks, never secrets. Decisions go to .bimai/decisions/, not into
history. The files are plain text, so you can read and correct them yourself.
Changing your team
Edit the team list in your seat.yaml, then run:
bimai team # or: bimai team --dry-run to see what would change# .bimai/seats/anna/seat.yaml
team:
- { role: coordinator, why: Always }
- { role: model-checker, why: "Goal: model-checks · Data: Revit" }
- { role: planning-analyst } # added by handbimai updates the team files in .claude/agents/, the routing table in CLAUDE.md and your
team.md. A member you remove loses its file in .claude/agents/ but keeps its history. bimai only
touches files it wrote itself: an agent file you wrote by hand is never changed or deleted.
bimai validate catches unknown roles, a role listed twice, and teams over five.
Coming later:
bimai team reviewsuggests removing members you haven't used for four weeks, and adding one when new data or goals appear. Nothing changes without your confirmation.bimai onboard --updatere-runs the interview when your role or the project phase changes.- Removing a member keeps what it learned, so adding it back later restores it.
See your team
bimai graph teamdraws your team, their models and the tools each may use, as a diagram in VS Code.