suggest-loop

Generation exercise, not template fill. Turn a repo's verification signal into /loop prompts a "vibe coder" can paste as-is — someone who can't author a precise loop prompt, so the repo proposes it and they just approve or tweak. The failure mode: a confident-sounding loop with no measurable "done".

Read this first — the load-bearing constraint

Do not reason about /loop from memory. The vendored reference is the authority: harness loop mechanics change faster than any model's priors, and a session reconstructing them from memory gets them wrong (that's why this skill exists). Read references/loop-mechanics.md before emitting any suggestion — every claim about how /loop behaves comes from there, not priors.

Recipe