Loop engineering — designing loops that prompt the agent

The practical discipline behind the slogan that you should stop prompting agents and
start designing the loops that prompt them. Students learn the canonical cycle —
plan, change, validate, observe, revise — and how to wire it: project instructions as
reusable rules, tools and connectors for the agent to act through, work isolation
(branch, worktree, container) so a run cannot damage production, and a built-in
verification step. They learn the bundled /loop-style skill pattern (e.g. a loop
that babysits open PRs, auto-fixes build breaks, and addresses review comments in a
worktree) and the principle that loops calling sharp, named skills get cheaper over
time while loops that re-derive everything do not — a direct tie to the compound
step of EB-10.