Gabba Works

Gabba Builds · 13 November 2026

Our house rules hit 64 versions. So we started cutting.

Conceptual AI illustration: a builder in a dark jumper types at an open laptop on a wooden desk, while a small white robot sits on a short neat stack of blank paper. Warm window light, a blank monitor, and houseplants are in the background.

The shared rules for my AI agents hit 64 versions in 22 days. That's about three edits a day. Most of them were a new check or a new guard, added after something went wrong.

I was trying to be careful. What I actually got was a process that was mostly checks on checks. The agents had to keep re-learning the rules as they changed.

We were adding steps to satisfy too much caution. If we break something, we can fix it. So I wrote the order down, and this week the agents are stripping their own workflows against it. I don't have the results yet. This is the rule, and a prompt you can give your own agents if your process has gotten heavy too.

My agents run on Grok Bot, which comes out of Elon Musk's SpaceX, so it made sense to cut them back with his five-step algorithm.

Where the five steps come from

It's Musk's five-step algorithm, in his order. I wrote it so I can hand it to a coding agent and get a keep/cut list back.

  1. Question every step. Each step has to name who asked for it and why. A step nobody can name gets deleted.
  2. Delete before adding. Cut until you've probably cut too much, and about one in ten items has to be put back. If nothing comes back, you didn't cut enough.
  3. Simplify what's left. Only after the cuts do you make the remaining steps simpler.
  4. Speed it up. Then make it faster.
  5. Automate last. Never automate a step that should have been deleted.

It's easy to jump to a quicker script or a new automated check. That's how we got the 64 versions. Automating a step you should have deleted just makes the wrong thing happen faster.

A useful test for the first step is to walk the last thing your agents did, line by line, and ask those two questions out loud. "We always do a review here" is not a who and a why. If you can't name the person who asked for that step, and the failure it was meant to stop, it goes on the cut list.

Two extra rules, and what stays checked

We added two more, because the five steps on their own don't stop the file growing tomorrow.

Undo beats caution. If a mistake can be reversed with git, a rerun or a revert, do it and fix it if it breaks. Checks only go in front of work that can't be undone.

One-in, one-out. Any new rule, check, file or step has to replace or delete an existing one. The temptation, once you write a rule like this, is to add another one that protects it. That's the habit this is meant to break.

Some things stay checked, because you can't undo them: messages sent as you, money, deletions, secrets, and production changes. Everything else is fair game.

A prompt you can give your own agents

Copy this, point it at your workflow, and ask for a list before anyone cuts anything.

Go through our workflow and write a keep/cut list.

For every step, check, rule or file: name who asked for it and why. If nobody can name that, mark it for deletion.

Then cut. Keep cutting until you've probably cut too much, so that about 1 in 10 items has to be put back. If nothing needs to come back, you didn't cut enough.

Don't add anything new. Don't simplify, speed up or automate until the cuts are done. Never automate a step that should have been deleted.

If a change can be undone with git, a rerun or a revert, don't add a check in front of it. Checks stay only in front of work that can't be undone: sending messages as me, money, deletions, secrets, and production.

Any new rule, check, file or step has to replace or delete an existing one.

Don't apply any cuts yet. Give me the keep/cut list, the reason for each cut, and what you'd put back.

Don't let the agent apply the cuts until you've seen the list. If it has no put-backs, the cut wasn't deep enough, and you should send them back to cut more.

What's next

I don't know yet how many steps will go, how many rules will come out of the file, or which ones we'll have to put back. The rules file grew when this rule went in. That's fine. The test is whether it shrinks once the cuts land.

I'll write a follow-up next week with those numbers: what we cut, what we put back, and what the rules file looks like after. If we never put one back, I'll say that too, because it would mean we didn't cut enough.

See you next week,
Gabba