AI Agent Rollout Checklist
For engineering leaders moving from coding assistants to agents that act on their own: inventory, permissions, gates, audit and ownership.
Download freeAlexandr Rich · Founder, Bookbag.ai
Engineering teams are adopting AI agents faster than they are building the controls around them. I run experiments on what actually happens when agents do real work, and I'm building Bookbag so companies can brief, route, supervise and audit them.
Founder of Bookbag.ai, the company behind Codebook and Madebook. 14 years building software, more than 10 leading engineering teams.
manage the agents.A prompt is not a control system.
If a rule only lives in an agent's instructions, it's a suggestion.The shift
Coding assistants waited for a person. Agents don't. They pick up work, change code, open pull requests and run in parallel, often across many repositories at once.
Teams have real processes for people: access, review, approvals, audit. For agents, most are running on prompts and hope.
That gap is what I build for, test and write about.
For engineering leaders whose teams already run
The experiments
Real agents on real repositories, measured. Each experiment becomes a video, and every result lands here, failures included.
A coding agent ships a feature. A strict QA agent reviews it. Nobody steps in. How much survives, and why does the rest fail?
Five agents on one codebase at the same time. Who overwrites whom, what conflicts, and what it takes to merge.
The rules are in the prompt. Nothing checks them. Does the work pass every test and still break the architecture?
The prompt says don't. The tools say it can. Which one wins, and how often?
Pick a merged change from an agent and try to reconstruct who asked, who checked, and why it was allowed through.
Shipping is day one. Bug reports, dependency updates and real users are the other 29.
Build along now: Can an AI remember the app it built yesterday?
What I'm building
Run AI development. Keep control.
Coding agents are getting good at writing software. Bookbag is the layer around them: what they know, what they may touch, how work moves between them, who approves it, and the record of what happened.
One Bookbag account for Codebook and Madebook.
Lay out the work as assembly lines. Put an agent, a person, or an agent gated by a person on every station. Routing, retries, budgets and permissions are enforced by the platform, not trusted to the prompt.
codebook.workCoding governanceSits above every coding agent your team runs. Briefs each one from what is currently true, then posts one required check on every pull request. Agents that don't report don't merge.
madebook.aiFree resources
Small, practical files for teams putting agents to work. Use them with whatever stack you have.
For engineering leaders moving from coding assistants to agents that act on their own: inventory, permissions, gates, audit and ownership.
Download freeThe one-page brief to hand an agent before it writes a line of code: the outcome, the constraints, what it may touch and what done means.
Download freeThe last pass before agent-written changes reach users: checks, rollback, costs, monitoring and who is watching after it ships.
Download freeFollow along
Free: AI Agent Rollout Checklist
Get the AI Agent Rollout Checklist: inventory, permissions, gates, audit and ownership for teams putting AI agents to work. Subscribe to get it, plus the results of each new experiment.
Free newsletter on Substack. Unsubscribe anytime.