How do I set up Claude Code for a team of 5 to 15 developers?
By Soumen Sarkar · October 2026
Short answer: Give everyone the same short CLAUDE.md, one shared memory for what changes by the hour, and the same three instructions: state assumptions instead of stopping, record decisions as you make them, and leave a handoff when you stop. Then run parallel sessions in worktrees, and review by reasons.
What should be the same for everyone?
On rollout day, decide these once and commit them:
- A short project CLAUDE.md: build and test commands, conventions, folders not to touch, and a line saying where live decisions are. Keep anything that changes week to week out of it. See why our CLAUDE.md keeps growing.
- One shared memory every session reaches, so sessions know what teammates' sessions are changing, decided and assumed. See how do I share memory across my team's Claude Code sessions?
- Three agent instructions:
- state your assumption and keep going when something is unclear (assumption);
- record decisions as you make them;
- leave a handoff when you stop before you're done.
How should people run sessions?
- One task per session, in its own worktree. Worktrees keep sessions out of each other's files; the shared memory keeps them out of each other's way. See do git worktrees stop parallel agents conflicting?
- Two to four sessions per person is a common rhythm. More than that and reviewing what comes back becomes the work. See how many agents can one developer run well?
- Say what your work will become when it touches a shared area, so other sessions build on it.
How should the team review and follow along?
- Review by reasons. Each change carries what it's for, what was decided and what was assumed; the reviewer reads those first. See reasons.
- One place to look each morning: assumptions to answer, decisions that replaced others, what landed.
- Let the rest of the company follow from a link, in plain words, instead of a weekly demo.
How long does it take?
The files take an hour. Campfyrr covers the shared memory, the instructions and the morning view as one Claude Code plugin, installed per person in a couple of minutes. See shared team memory for Claude Code.
Words used here
- Assumption: An assumption is the best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
- Handoff: A handoff is what unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
- Reasons: Reasons are what a change is for, the calls made in it, and what was assumed, attached to the change for whoever reviews it.
- Area brief: An area brief is what a person or agent is told the first time they touch a part of the code: what's changing there now, what was decided, and what was tried.
The principle behind this: Keep moving: The work never waits, and neither do we.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).