The 5-Wave Operator Playbook
A written operating model: how to inventory the work, fence two pieces of it so they can run at once, dispatch them with one real approval gate, verify what comes back with evidence rather than trust, and leave something behind so the second time costs less.
Five chapters · one exercise each · none of them need a PhoneAgents account
Every chapter follows the same five-part shape, so you learn one structure and apply it five times:
And how much of it is waiting on you personally. Nothing can run beside anything else until the work is visible.
You end with: a written work list with the operator-blocked items marked.
A boundary written in one line each. This single sentence pair is the whole technique — everything after it is a consequence.
You end with: two non-overlapping write scopes — your first real fence.
Publishing, deploying, sending, paying, deleting. You decide in advance which of them stop and wait for you.
You end with: one parallel run, one explicit approval gate, and a merge ledger.
An evidence rule: what proof each kind of work has to return before it counts as finished.
You end with: a written evidence rule you can hand to someone else.
Because the first solve left nothing behind. Memory comes last because it only pays once there is something worth remembering.
You end with: one reusable artifact — a prompt, checklist or template — that wave 6 starts from.
The five waves are about how an operator gets to running waves at all — inventory before fencing, fencing before parallelism, parallelism before verification discipline, memory last. It is the operating model PhoneAgents itself is built with; the site's BMad phases describe what happens inside one wave, and this describes how you get there.
Get it
We email you the playbook. If you would rather know where you stand first, the 12-question scorecard scores you in your browser — no address needed to see the number — and the emailed version adds a breakdown of which dimension is holding you back.