The Build Loop
A steady rhythm of planned, briefed, shipped slices.
Last updated 2026-08-13
Building software with Leefy is a loop, not a waterfall: a planning agent turns a branch into sliced briefs, you approve them, and then slices ship one at a time — each one briefed, run, harvested, and banked before the next begins.
Leefy stays authoritative on the what (goals, acceptance criteria, scope); the coding agent grounds the how in your actual repo at session time. The Accept gate and the premise check are where those two meet honestly.
- 1
Plan the work
Plan sessionRun a Plan session on the branch you want built. A coding agent explores your repo and returns an ordered set of slice briefs, each with a run-with recommendation.
You’re here when: A branch holds the intent, but there is no ordered queue of slices for it yet.
- 2
Accept the plan
Outside LeefyReview the returned briefs at the Accept gate — edit what reads wrong, park what can wait, approve the rest. Accepting plants the slice queue under the branch.
You’re here when: A plan summary has been pasted back and is waiting for your review.
- 3
Take the next slice
Run the workThe queue always knows what is next. Assemble the slice prompt — instant, straight from your accepted brief — hand it to the agent, and let it run.
You’re here when: The queue shows an up-next slice that is not yet in motion.
- 4
Ship it and mark it done
Mark donePaste the session summary back and harvest it. Watch the premise check — anything the brief got wrong shows up amber. Mark the slice done and the queue advances.
You’re here when: A session has come back with a summary ready to bank.
- 5
Review, then go again
ReviewSkim what shipped and let it correct the plan: revise briefs that drifted, then take the next slice — or run a fresh Plan session when the queue runs dry.
You’re here when: Slices are landing and the loop is turning; the question is only what turns it next.