Loop Engineering

Stop prompting your coding agent by hand. Design the loop that wakes it, gives it a job, checks the result and knows when to stop — then let it run. This guide explains how loops work, why the stop condition is the hard part, and how to point loops at your own product so it improves itself while you keep the decisions.

Written by the team behind Tekk, which runs twelve loops on your codebase so you don't have to engineer them.

Read in order

Start with what a loop is, then how it connects to spec-driven development and compound engineering, then how to run loops on a real product.

Let your product improve itself.

Connect your repo. Twelve loops start watching your code and bring you proposals — you greenlight them, your coding agent builds them.