- anti-spin-build-loop.md 45 lines · 2.6 KB
Anti-Spin Build Loop
Loop Engineering — most agent loops never stop to ask whether they're actually making progress, so they retry the same broken approach or quietly edit the test to pass. This loop runs build → audit → verify against a machine-checkable contract, with explicit stops that detect spinning.
🎯 Goal
Drive toward a verifiable contract while actively guarding against the classic failure mode: an agent that loops forever without converging.
⏱️ Schedule
Suggested interval: 15m.
▶️ Run it
/loop 15m "Build toward the goal, then audit and verify against a machine-checkable contract. Track progress each pass. Stop if you make no progress, repeat an approach you already tried, flip-flop between two approaches, or hit the budget. Finish only when the contract passes — never by weakening the contract or the tests."🔁 Iteration steps
- Build — advance toward the contract.
- Audit —
architect-reviewchecks the change;scope-guardblocks weakening the tests/contract. - Verify — run the machine-checkable contract; record progress vs. last pass.
- Anti-spin check — no progress? repeated approach? flip-flop? budget hit? → stop and report.
- Observe — if making progress and contract not yet met, loop; else
/pr-reviewand hand off.
🛑 Stopping condition
Contract passes, or an anti-spin guard trips — whichever comes first.
💰 Budget & guardrails
Hard caps on iterations and spend; no-progress, repeated-approach and flip-flop detection. The contract and tests are immutable — the loop may not edit them to "pass".
🧩 Referenced components
agent:expert-advisors/architect-review— independent audit each pass.command:git-workflow/pr-review— structured review at handoff.hook:quality-gates/scope-guard— prevents weakening tests/contract to fake success.
💡 Example
Chasing a contract for a parser, the loop tries approach A, then B, then drifts back to A — the flip-flop guard trips and it stops with a clear report instead of burning tokens forever.
Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-17
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.