projects / turbo-flow
Turbo Flow
Turbo Flow is the agentic developer environment that made governed agent work ergonomic: spin up a complete agentic workflow — plan, research, build — in minutes instead of days.
It is open source, and it taught the lessons that became Turbo Rig.
What it does
A developer environment, not a framework: Claude Code and other coding agents at the center, containerized and reproducible, with the workflow scaffolding — planning, PRDs, ADRs, swarms, verification — wired so a newcomer can be productive with agents in a first session instead of a first month.
The arc that matters
Complexity → observation → redesign 3,181 lines → ~160 5 scripts · 1 gate · human merge
Turbo Flow grew into a 3,181-line orchestration system — swarms, hooks, memory, everything. It worked, and it was too much: more agents did not mean better engineering. The v5 lean pivot cut the core to roughly 160 lines and five scripts around a single hard idea: one cross-model review gate, with humans retaining merge authority.
That idea, extracted and hardened, became Turbo Rig. The lesson — subtraction over addition — is now the first design question I ask in every engagement: what does this replace?
In other people's hands
Turbo Flow is not just my workflow. Jan Lafko, 22, used it to plan, build, and sell a customer website — then wrote tf-verify, 220 quality gates for the container, and donated it to the project. An environment people extend voluntarily is the only adoption metric that counts.
Talk it through with someone who runs this stack on his own systems every day.