THE DELIVERY FRAMEWORK
FOR CODING AGENTS
AGENTS SHIP.
YOU STEER.
Describe the feature once. Coding agents plan it, build it test-first and open the pull requests. Your team owns the product and the rules, and sees every decision the agents took.
- ONE FOLDER IN, ONE FOLDER OUT
- EVERY DECISION WRITTEN DOWN
- A PERSON ALWAYS MERGES
“TO JOIN INSTANTLY,
SIGN UP WITH GITHUB!”
Strategy guide: the loop
- 1-1 IDEA: You talk an idea through with Claude. Nothing is written yet.
- 1-2 PRD: The idea becomes a brief and a before/after page. A person approves it before any code exists.
- 1-3 INBOX: Approved and ready to build.
- 1-4 OUTBOX: Agents build it in slices, test-first. Every decision they took without asking waits for your answer.
- 1-5 SHIPPED: A person reviews and merges the feature, never an agent.
- 1-6 RETRO: How the delivery went, and what it taught.
- ★ BONUS KNOWLEDGE: What you settled becomes the rules the next idea starts from.
- YOU: a person decides, with Claude for the idea
- AGENTS: coding agents build every slice
- OMNI APP: opens the retro on GitHub
Built for your customers
The agents don't build for you. They build for your customers. Tell them who those are once, and every run reads it.
EXAMPLE Brick & Bolt: Software for renovation firms, up against the spreadsheet.
BUSINESS
Who you sell to.
- SIZE
- 5 to 50 people
- REGION
- Europe
- TRADE
- Renovation firms
- RIVALS
- The spreadsheet
PRODUCTS
What you sell them, one product at a time.
- Site Diary: A site diary app: the day's work, photos and hours, logged from the site.
PERSONAS
The people who use it.
- NadiaOffice managerEXCITED
- TheoPlumber, subcontractingNEUTRAL
- MarekSite foremanSKEPTICAL
THE AGENTS READ THEM ON EVERY RUN
Marek: “This approval screen expects a back office. My crew is five people and I sign off my own work.”
YOU: “We sell to 5-person crews too.”
★ KEPT: A crew may have no back office: the foreman approves his own work.
The game: build your fleet
Ship value to your customers, and score for your fleet while you do.
CREATE YOUR FLEET
EXAMPLE A fleet is a team with a name, a colour and a mascot.
Hover, tap, Enter or Space flips a card.
SHIP VALUE
A secured zone scores 10. A rescue scores 20. Closing Entropy (an unanswered question, stuck work, a shipped bug) scores 5 to 25, by its kind.
CLIMB THE LEADERBOARD
EXAMPLE The fleets above, ranked by points.
- 1 GOLD DIGGERS 1415
- 2 DAM BUSTERS 1240
- 3 SEA DOGS 1105
- 4 DEEP DIVERS 980
- 5 SPY RING 760
THE LOOP BUILT THIS
FEATURES SHIPPED 95SLICES MERGED 460DECISIONS ADOPTED 710Counted from Omni Loop's own shipped work, each time this page is built.
Join the loop!
To join instantly: sign up with GitHub
Omni Loop runs on Claude Code. Free while in beta: sign up with GitHub.
Leave any time: delete one folder and commit. Nothing to migrate.
PSST: ↑ ↑ ↓ ↓ ← → ← → B A FLASHES CHEAT ACTIVATED! AND DROPS YOU IN THE GAME.