← ClaudeAtlas

gauntlet-looplisted

Use when a user asks to run a Gauntlet Loop, improve work against a concrete reference until it passes, turn a rough software request into an autonomous iterative quality run, or resume an existing .gauntlet effort in a new or existing project.
Yash-1511/gauntlet-loop · ★ 1 · AI & Automation · score 64
Install: claude install-skill Yash-1511/gauntlet-loop
# Gauntlet Loop ## Overview Turn a rough goal into a resumable evidence loop: initialize the project, keep a real quality bar fixed, divide only independently judgeable work, and route each failed artifact through a fresh critic until all gates pass or an honest stop condition applies. Core laws: 1. The builder never grades itself. 2. The critic inspects the real artifact, not a builder summary. 3. A supplied reference stays in the bar; a proxy cannot quietly replace it. 4. A failed round returns one largest gap and one next proof. 5. No reproducible evidence means no pass. ## Workflow ### 1. Initialize or resume Verify the harness can create fresh agent contexts and let them inspect files/tools. If it cannot, follow **No fresh-agent capability** in [role-contracts.md](references/role-contracts.md); do not fake independent criticism. Run from this skill directory: ```bash python3 scripts/init_project.py --project /absolute/path/to/project ``` Read `.gauntlet/project-context.md` and `.gauntlet/harness-assessment.md`. Then read [context-and-harness.md](references/context-and-harness.md) and inspect only the relevant repository instructions, docs, source, tests, and current changes. If resuming, refresh context and reproduce the best-known artifact before accepting old evidence. Preserve every pre-existing working-tree change as user-owned. ### 2. Anchor intent and choose the bar Write the user's verbatim request to `.gauntlet/request.md`. Do not polish or reinterpr