Agent skill · product strategy · affaan-m
loop-design-check
Design a goal-oriented agent loop or review one for failure modes: spinning, Goodhart-gaming the verifier, or running a wrong answer to completion. Covers machine-decidable goals, loop types, plan/build/judge skeletons, and runaway prevention; mechanism wiring lives in autonomous-loops. Use when designing, writing, or checking an agent loop. 中文触发：写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不会跑飞、可判定目标、五个崩法、plan build judge。
Why this skill is useful
Adds a structured framework for designing and reviewing autonomous agent loops, including specific checks and balances that enhance goal-oriented behavior.
What it needs
About 8k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Loop Design + Review Premise. An LLM is a feed-forward system: prompt in → tokens out, with no built-in "steer toward the goal" across turns. To make it behave like a goal-oriented system, you wrap a feedback loop around it. This skill helps you write that loop correctly and review it so it won't run away. When to use / not Use it when: You want to hand a repeating task to an agent that runs over and over (write→test, test→fix, fix→verify…). You already have a loop and worry it spins, cheats, or runs a wrong answer to completion. Don't use it for: A one-off task → just do it; don't wrap a loop around it. A plain timer / poll → use /loop; no design needed. How to wire the loop architecture (pipelines → DAGs, long-run recovery) → that's the mechanism layer; see autonomous-loops / continuous-agent-loop. This skill only covers "is the goal right, and will it run away" — it does not re-explain mechanism. Red-line premise: two levels of feedback Level Who owns it What it does --- --- --- Execution (low) machine / agent Measures "how far from the literal goal" and grinds it to zero. The machine is strong here. Judgment (high) human Decides "is this goal itself right, should it change, should it stop." The machine can't step outside its own loop to question the goal. A thermostat can feed back "how far from 26°C," but when you have a fever and want 28°C it can't judge whether 26 is the right target — it just grinds toward 26. "What to set today" is always the human's call. Handing judgment / sign-off / the last switch to the machine = removing the high-level feedback = it sprints, fast and hard, toward a goal no one questioned → wrong output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/loop-design-check