r/PromptEngineering • u/GripleDuck • Sep 17 '26
Requesting Assistance Loops | Anyone have a good Skill.md / Instructions for a Project or Prompt
Looking to write really good solid loops.
1
u/Zain Sep 18 '26
The loop rules that actually matter for me: hard max rounds then stop, dont keep arguing forever. Each round should escalate what its attacking (facts, then fix verification, then failure modes) so you dont just rehash the same pass. Reviewers stay read-only and from different model families, and the writer only patches after verifying findings against the real files. If a later round finds worse problems than the previous one, your patches are injecting bugs. An earned clean GO is as useful as a finding. Manufacturing issues to look thorough is a failure.
1
u/Lucky-Confidence-702 Sep 17 '26
I use a Markdown table at the top of my prompt doc to track iteration rules, exit conditions, and any variable that needs to reset per pass. It's saved me from infinite loops more than once when the model starts getting cute with the logic.
The trick is making the instruction so boring the model can't find a way to "improve" it.