Agent Loops for PMs: The Hard Part Is the Stop Condition
This article explains agent loops for product managers, distinguishing between routines, workflows, and true goal-driven loops. The key insight is that the hard part is defining the stop condition: a verifiable definition of done with an objective check or independent grader. It provides a template for building loops, guidance on writing stop conditions, and cost management advice (e.g., tracking cost per accepted change). Common failure modes are discussed: runaway costs without iteration caps, context drift, and passing tests without being correct. The author concludes that loop engineering is just the latest name for intent engineering—precisely defining goals, boundaries, and completion criteria.