Integrating an Agent into Team Workflows

Up to now, this entire course has been about you, alone at your machine. Moving to a team changes three things at once, and that's where most adoptions go wrong: the volume of proposed code goes up while review capacity stays flat, the project's conventions no longer live in a single head, and the question of who answers for the shipped code stops being theoretical.

The symptom is easy to recognize. Three months after the tool arrives, the team produces more pull requests, they're bigger, review becomes a rubber stamp, and production incidents increase with nobody able to say which ones to attribute to what. None of these three trends is caused by the agent: they come from a process that hasn't been adjusted to a much higher output rate.

The Conventions File Is a Team Artifact

You've used CLAUDE.md as a personal notebook. On a team, it changes nature: it becomes the one place where the project's implicit conventions are written down, and it's versioned alongside the code.

This shift has a side effect that is often more valuable than the productivity gain. Writing a convention for a machine forces you to state it unambiguously, something that word-of-mouth transmission between developers lets you avoid for years. The first serious draft of this file usually surfaces two or three disagreements the team didn't know it had.