gauntlet-loop

Coordinates iterative builder and critic rounds to improve artifacts against an inspectable bar.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill gauntlet-loop-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gauntlet-loop
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/gauntlet-loop
Command: npx skills add https://github.com/mintuz/.dotfiles --skill gauntlet-loop-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambitious artifacts often ship with unverified quality because the same agent both builds and judges its own work. This Skill separates builders from fresh critics and loops until direct comparison evidence shows the artifact meets a concrete, inspectable bar. ## Core Features & Use Cases - Bar Definition: Establishes an observable goal, comparison method, materiality threshold, and stop policy before any building begins. - Builder/Critic Separation: Assigns builders isolated git worktrees while fresh critics judge artifacts blind, returning WIN, LOSE, or UNJUDGEABLE verdicts with evidence. - Convergence Ledger: Tracks rounds, verdicts, gaps, and repairs in a compact table, stopping only on a win, resource limit, or sub-threshold remaining gap. - Use Case: Iteratively refine a UI redesign by pinning a rendered reference and capture protocol, then running build-and-judge rounds until screenshots match the bar or the budget is exhausted. ## Quick Start Run a gauntlet loop on my landing page redesign against the reference screenshot, with a budget of six rounds and a stop threshold for pixel-level differences.

Frequently Asked Questions about gauntlet-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an iterative build-and-critique loop with AI agents?

Define an observable goal and inspectable bar first, then assign builders to produce the artifact while separate fresh critics judge it blind each round. Critics return WIN, LOSE, or UNJUDGEABLE with direct comparison evidence, and the loop repeats until the artifact wins or a stop condition is reached.

What is a good stopping condition for iterative artifact improvement?

Stop only when the artifact wins against the bar, the user stops the loop, a named resource limit is reached, or remaining gaps fall below an agreed materiality threshold. Exhaustion of rounds is a stopping reason, never evidence that the bar was met.

Why should the critic not see the builder's history or rationale?

Withholding builder history, summaries, and claimed quality prevents the critic from being anchored by the builder's self-assessment. A fresh critic inspecting only the artifact and raw evidence produces an unbiased verdict grounded in direct comparison.

Can multiple builders work in the same git repository safely?

Yes, by giving each builder its own git worktree on its own branch, since worktrees share one stash list and stash use can restore another builder's edits. When only a shared worktree is possible, builders run no git write commands and the lead commits each builder's files separately.

When should I not use a gauntlet loop workflow?

Avoid it for routine changes with clear acceptance tests, where the overhead of separate builders and critics adds no value. It is designed for ambitious artifacts whose quality bar requires independent judgment and repeated evidence-backed rounds.