Reference / Workflow Map

Workflow Map

Becky builds context the way a real team does — progressively, across seven levels. Each level produces something the next one needs, so the agents always know what to build and why. Three modes move work through those levels: greenfield, brownfield, and the war room.

Greenfield ↓ Brownfield ↓ War Room ↓

The seven levels

Every agent lives at one level. Work flows left → right; nothing advances until its gate passes. Scroll the strip →

How to read it: a level is a stage of understanding (Frame → Plan → Design → Build → Harden → Gate → Ship). A mode (greenfield / brownfield) is a path that visits these levels in order. The war room pulls every level into one room at once.

Greenfield — build something new

From "is this even worth building?" to "it's tested, verified, documented, and announced." The full origin story — fourteen phases across all seven levels. Start it with one command:

greenfield

$ becky greenfield "checkout redesign"

Cross-cutting: three agents aren't a phase — they're always on. Friday traces the blast radius of every diff during Build; Xavier is on-call for "how does the domain handle X?" across phases 1·3·4·5·6·11; Watcher runs continuously and closes every task. Three hard gates (7 · 12 · 14) have no path around them.

Brownfield — work on existing code

Archaeology first. Understand what's really there — not what the docs claim — before you touch a line. Eleven phases that protect what already works.

brownfield

$ becky brownfield "fix the checkout bug"

War Room — all 15 on one problem

Not a phase — an event. When you're stuck, facing a P0, or staring down a decision that splits the team, every agent convenes on a single problem. The value is in the tension between perspectives.

assemble

$ becky assemble "checkout is failing silently"

Modes — how you start, what it loops on

The pipeline above is the engine; modes are how you drive it. Every loop stops on independent, runtime-grounded verification — never on an agent saying "done." A budget cap can stop a loop early, but then it reports exactly what's still red. That honesty is the whole point.

One more thing: every phase is self-contained — it reads inputs from a known place and writes outputs to a known place. That's why the whole pipeline can run unattended with becky autopilot. Read the Field Manual →