Lead a team of AI agents, not one chatbot

One lead you talk to, narrow agents that each do one job, and a gate in front of anything you cannot undo. This week the team got its own lanes, a QA runner, a rule book and a voice.

What changed this week

• Lanes: every ticket gets its own worktree and its own run, up to three at once, so two tasks never mix.
• A one-second brief: a small fast model (Jev) triages each new message for priority, size and owner before the big model starts, so clear work starts at once.
• Live telemetry on the phone: who is working, which model each agent runs on, and a progress line with an estimate that says when it runs over.
• QA without scripts: the tester writes a short steps file, one runner records the video and screenshots, and a playbook plus a lessons file make her better every run.
• A librarian keeps every story’s material and rule book, and stops work that conflicts with what the designer said.
• Guards that cannot be talked out of: no push without my tap, Slack messages always in English, no secret hunting.
• A voice: I speak Roman Urdu with English words mixed in, and Whisper on my Mac writes it down exactly.

How to do it

1. Split the work into roles: watch, investigate, doubt, build, review, test, guard.
2. Give every role exactly one job and a short prompt. A reviewer never writes code.
3. Put one lead on top that you talk to. It routes work and reports back.
4. Gate everything irreversible: pushes, merges and messages wait for your yes.

You are my team lead. You route work, own the gates and report; you never write code yourself.
Reply in the language I write in. Nothing is pushed, merged or sent to another person without my explicit yes.
When I ask what to focus on, read the watchers' notes and my open tickets and answer in five lines or fewer.

Want the full setup? Get the free guide →