{"slug": "how-i-code-with-a-team-of-ai-agents", "title": "How I Code with a Team of AI Agents", "summary": "A developer packaged a multi-agent coding workflow as a Claude Code plugin called Larceny, in which a coordinator agent splits work into small tickets, assigns them to four parallel coding agents, and routes every pull request through an adversarial reviewer agent before merge. The setup is designed to keep diffs small and reviewable, with escalation to the human owner after repeated review rounds, and the developer reports the crew built most of Larceny itself.", "body_md": "I run my software shop with a team of AI agents. I talk to one of them, a coordinator, and he plans the work, splits it into small tickets, hands them to four coding agents and makes sure a reviewer checks every pull request before it merges. I packaged the setup as a Claude Code plugin called [Larceny](https://github.com/nestedmind/larceny).\n\nPeople code with AI in two main ways today. The first is AI-assisted programming, where your editor sits in the middle, a chat sits on the side, and you accept or reject each change the AI suggests. The second is agentic coding, where you tell an agent what you want and it goes away and builds it.\n\nI used the second way and kept hitting the same problem. Take a login feature. If I gave one agent the whole thing, it went away for a long time and came back with a login page, a large diff and a lot of slop. Then I either spent hours reviewing it or started rewriting it because the UI wasn't what I wanted. The agent wrote the code faster than I could read it, so I became the bottleneck.\n\nI wanted the agents to work the way a good engineering team does, with small tickets, parallel work and code review, and I wanted to hand the coordination to them.\n\nThe team has a coordinator, four coders and a reviewer. There's also an advisor I use to question the coordinator's decisions, and a teacher who explains anything I don't follow. I'm the owner.\n\nWhen I ask for something, the coordinator turns it into tickets on a project board, works out which ones can run at the same time, and assigns each one to a coder. The coder builds its ticket on its own branch with tests and opens a pull request.\n\nThe reviewer is set up to be adversarial. She looks for problems, leaves inline comments and sends the work back until it's right. If a review goes to a third round the coordinator steps in, and at the fifth round it escalates to me. Once the reviewer approves, the work merges and the coordinator reports back.\n\nThe default crew is named after characters from Prison Break, a TV series about a man who breaks his brother out of prison. Scofield is the coordinator, and Sucre, Mahone, Whip and Sheba are the coders. The reviewer is Amy from the police sitcom Brooklyn Nine-Nine, the advisor is Yoda and the teacher is Sara. You can rename any of them during setup. I've run a crew from Game of Thrones on another project.\n\n`gh`, signed in.\n**Smaller diffs.** Each ticket is small, so each pull request is small enough for a person to read in one sitting. I'd argue massive diffs aren't good for agents either, because a reviewer agent catches more in a small change.\n\n**Faster delivery.** Tickets that don't depend on each other run in parallel.\n\n**Traceability.** Every change has a ticket, a branch, a pull request and a review thread.\n\n**Review before merge.** The reviewer checks every pull request, and I only get pulled in when the agents can't agree.\n\n**Time on planning.** Agents now do most of the implementation, so the slow part of building software has moved to the work before it. Andrew Ng calls this the [product management bottleneck](https://x.com/AndrewYNg/status/2043742105852621052). So I spend my time writing tickets with the coordinator, and other engineers review them before any agent starts. That's where we argue about trade-offs and decide how something should be built. Each ticket then links to its pull request, so reviewing the code means checking it against what we already agreed.\n\nInside Claude Code:\n\n```\n/plugin marketplace add nestedmind/larceny\n/plugin install larceny@larceny\n/larceny:onboard\n```\n\nThe crew built most of Larceny themselves, so the repo's tickets, pull requests and reviews show the workflow in practice.\n\nI'd like to hear from anyone running several agents against one repo. How do you stop review from becoming the bottleneck?", "url": "https://wpnews.pro/news/how-i-code-with-a-team-of-ai-agents", "canonical_source": "https://dev.to/0xschool/how-i-code-with-a-team-of-ai-agents-10fh", "published_at": "2026-10-01 19:25:22+00:00", "updated_at": "2026-10-01 21:31:07.105956+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "large-language-models"], "entities": ["Larceny", "Claude Code", "GitHub", "Andrew Ng"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-i-code-with-a-team-of-ai-agents", "markdown": "https://wpnews.pro/news/how-i-code-with-a-team-of-ai-agents.md", "text": "https://wpnews.pro/news/how-i-code-with-a-team-of-ai-agents.txt", "jsonld": "https://wpnews.pro/news/how-i-code-with-a-team-of-ai-agents.jsonld"}}