From Prompt to Loop.
Prompts made you faster. Loops make your whole team faster. A sharp prompt makes one engineer more productive for an afternoon. A loop, a small system that runs an agent for you on its own, makes the whole team more productive every day, on a schedule, whether you are in the chair or not.
This is the manual for building them without burning money or breaking production. Thirty nine pages, written so a beginner can follow it and an operator can ship from it.
The industry worked out the loops that build. This guide is the loops that operate.
Get the guide
All 39 pages: the nine rules, all thirty five loops, and the operations playbook. Just your email, no spam, unsubscribe whenever.
What is inside the guide?
- The shift, in three rungs, and why most people are stuck one rung too low
- The nine rules the toolmakers actually follow
- A five question test for whether something is a real loop or a chore in disguise
- All thirty five loops, sorted by the job they do: engineering, cloud, AI, and QA
- A five day plan to ship your first one, and one built in full you can copy
- The starter pack: a real rules file, a hook, and a working CI workflow
- The same loop mapped onto Codex, so it works with whichever tool your shop pays for
- The operations chapter nobody writes down: where loops run, what they remember, what they cost, how to secure a fleet, and how to stop one that goes wrong at 3am
Who is this guide for?
Founders, engineers, and operators who already use an AI coding tool a little, feel the productivity is real, and suspect they are leaving most of it on the table. You are. This shows you where it went.
Every command is shown for Claude Code, because that is what I run. It all maps onto Codex one to one, and there is a translation table in the guide.
Then run one
The guide ends with a build plan, not a summary. Pick the loop with the lowest blast radius, point it at your repo, and let it open a pull request you approve. That is the whole shift: from writing the software to building the system that writes it.
Crews, not committees. Loops, not turns.
About the author
Marios Fakiolas is a technology entrepreneur and leader with more than twenty-five years building teams and shipping products. He has led engineering as a CTO and founded companies. Before technology, he spent thirteen years as an officer in the Hellenic Navy and commanded a warship with a crew of twenty for thirty months.
Get in touch
Questions, feedback, or just want to say hello?