One mind, an army of agents: how I ship like a team
How I build with AI coding agents: specs, specialist agents, reviews and tests. 879 commits in 2026, and the rules that keep the work mine.
In 2026 I authored 879 commits across my repositories. I shipped a hospital maintenance platform, the integrations layer of a startup, a set of developer tools on npm and PyPI, and a real-money World Cup pool with more than a thousand bets. I did not do it by typing faster. I did it by changing what my job is.
I set the vision, agents multiply the hands, and I own every result.
The spec is the product
An agent is only as good as the instructions it receives. So most of my time goes into the part no model can do for me: deciding exactly what should exist. What the user does, what the edge cases are, what must never happen. A clear spec turns an agent from a guesser into a builder.
Specialists, not one generalist
In ATLAS, the paperwork engine I built for a hospital's engineering department, the repository includes dedicated agent definitions for different roles: interface, user experience, product management and agent architecture. Each one gets the context for its job and nothing else. It works for the same reason teams do: focus.
Every line is reviewed
Agents write a lot of code. Some of it is wrong. The commit history shows AI coding agents as co-authors across my projects, and every one of those commits went through review before it shipped. An agent's output is a draft until someone who understands the system accepts it.
Tests are the contract
When agents move fast, tests are what keep speed from turning into chaos. In ETHER, a permission suite signs in as every role every night and proves that nobody can see what they should not. In ZAVORA, the codebase carries thousands of automated tests. The rule is simple: if it is not tested, it is not done.
One mind. An army of agents. Full ownership.
What this changes
- The bottleneck moves from typing to thinking. The scarce resource is judgment about what to build.
- Small teams can take on big problems. A hospital platform, a startup's platform and a developer toolkit, in parallel, from Bogotá.
- Ownership does not delegate. Agents multiply the work. The responsibility stays with me.
Numbers from the git history of my repositories, January 1 to September 24, 2026. See the month-by-month momentum on the home page.