Estimated time to the first AI response: 2 minutes. Time to the first ready candidate: depends on what you are building, not the skill.
This guide assumes you have already installed the Gauntlet Loop. If you haven't installed it yet, see the installation guide first.
Inside the package, in templates/contrato-do-loop.md, there are ten sections. Only three are mandatory to start:
You don't need to fill out the other seven sections to run the first cycle. They exist for when the work justifies more control. If you want to see the expected level of detail, the package includes a complete example.
With the skill installed and the three fields filled in, paste something close to this:
Use a Gauntlet Loop to create [what you want]. My contract is below.
[paste the three fields you filled in here]
AI doesn't start producing. Before any draft, it confirms what is missing and asks at what depth the loop should run:
If you don't choose, it defaults to Essential. After the first version, it checks the criteria itself before presenting the candidate as ready. If any criterion fails, it states which one and why, instead of delivering it as if everything is fine.
The loop ends on the first of these events:
Stopping because the budget ran out is not a failure of the method. It is the method working. A real project using this skill reached seven cycles because the budget was increased midway, with a recorded decision. The complete case show how this looks in practice, including what hasn't improved.
After closing a loop, registration is voluntary: tell what you built. Help improve the material for whoever comes next.
Methodology created by Matt Shumer. Skill and materials adapted and structured by Israel Degasperi. Licensed under CC BY 4.0.