Browse topics Hub · essay · articles · FAQ · glossary

The compound loop — plan, work, review, compound

The methodology runs as a repeating loop that splits work into three phases: a human decides *what* is worth building, the agent plans/codes/tests/reviews an…

The methodology runs as a repeating loop that splits work into three phases: a human
decides what is worth building, the agent plans/codes/tests/reviews and prepares
the change, and a human judges whether the result is good enough and whether the
system learned anything reusable. Students learn the canonical loop (ideate →
brainstorm → plan → work → review → polish → compound) and the key insight that the
final compound step — not the code itself — is where the durable gains live,
because it is what turns a one-off feature into a system that builds the next
feature better. Steps are used à la carte: skip ideation when the target is known,
go straight to debug when the bug is obvious.

Sources