LoopFlow
Tutorial Workshop Keywords ๐ŸŽฎ LoopFlow Lab
Keywords / each cycle

each cycle

The repeated steps, in order. Core syntax

Syntax

each cycle: plan, then act, then observe

What it does

Defines the repeated unit of work โ€” the steps the loop runs, in order, on every pass until the goal is met. It's any subset of three verbs: plan reads context and decides the next move read-only; act makes the actual change; observe runs the done when check to see if the loop is finished. The full plan, then act, then observe is the default self-correcting unit, so you can omit the line entirely and get it for free.

You'd write the line to trim the cycle when a phase is wasted effort. A mechanical, well-scoped change often doesn't need a planning step โ€” act, then observe just does it and checks, saving a model call per cycle. On the other end, an ambiguous task benefits from keeping plan so the agent reasons before it writes. The order is fixed to the verbs you list; you don't invent new steps. Two related places also set it: a config-tier each cycle: at the top of the file sets the default for every loop below, and a loop's own line overrides that default just for itself. Whatever the shape, the observe step is what closes the loop โ€” it runs the predicate that decides pass (stop) or fail (reflect into the next plan), so a cycle without a way to observe can never end on its own.

Example

each cycle: plan, then act, then observe   # full self-correcting unit
each cycle: act, then observe              # skip planning โ€” just do + check
two shapes

How it runs

โœ“ pass planeach cycle actmake the change observerun done-when stopgoal met โœ“ when it fails โ†’ reflect, then plan again
Every cycle runs plan โ†’ act โ†’ observe; the done when check decides โ€” pass โ†’ stop, fail โ†’ reflect into the next plan.

Common mistakes

Related