B agent-loop-engineering

Execute an authorized software goal through low-context, bounded-autonomous AI coding loops with persistent state, proactive repair, automatic and functional evidence, layered stage review, independent final acceptance, safe workspace boundaries, and resumable handoffs. Use when a target and acceptance criteria are clear and the user asks to implement, debug, verify, continue autonomously, follow Controller-Developer-QC cycles, resume after context loss, or reduce repeated context and documentation. Typical triggers include keep going, continue where we left off, run it autonomously and fix what breaks, 接着跑 / 继续做 / 自动修 / 断点续跑 / 别再问我每一步, we are stuck on the same failure, 卡在同一个错误上, resume after compaction, 上下文快满了, stop burning tokens on repeated context, run the regression after this repair, and make a flaky test deterministic. Also use for bounded-autopilot, single-writer loop state, failure-signature stop rules, delivery-class-aware evidence, and anti-doc-bloat execution. For vague goals, legacy-state conflicts, requirement discovery, target rebaseline, scope creep triage, or QA acceptance authority, use cms-project-governance first.