agent-gauntletlisted

Multi-stage agent pipeline for feature development with deterministic quality gates - a specifier writes Gherkin acceptance criteria, a coder implements to green tests, a cleaner refactors until a complexity+coverage gate passes, a hardener kills surviving mutants via mutation testing. Use when implementing a user story with verifiable quality, when asked to "run the gauntlet", or when setting up quality gates for agent-written code.
n0an/agent-gauntlet · ★ 2 · AI & Automation · score 78

Install: claude install-skill n0an/agent-gauntlet

# The Agent Gauntlet Uncle Bob's multi-agent methodology, as a portable skill. Core idea: **don't stuff quality rules into prompts - wrap the agent in deterministic gates.** Agents treat written rules as vague suggestions and forget the middle of long instructions; tools don't decay. Put the agent in a loop against a checker until the numbers pass. ## The pipeline ``` story ──▶ specifier ──▶ coder ──▶ cleaner ──▶ hardener ──▶ (qa: phase 2) Gherkin + tests + CRAP gate mutation QA proc impl passes score clean ``` Each stage runs in a **fresh context** ("born, do the task, die") - this is deliberate. Handoff artifacts are files, not chat: `features/<slug>.feature` (Gherkin) and `features/<slug>.qa.md` (QA procedure) are the contract; the git diff is the payload. A fresh context per stage means no trajectory contamination from the previous stage's struggles. ## Stage contracts Run each stage as a separate subagent/session. Full stage prompts live in `stages/` next to this file (`specifier.md`, `coder.md`, `cleaner.md`, `hardener.md`, `qa.md`) - use them as the stage's system prompt, or read them and follow them directly if your harness has no subagents. Summary: 1. **specifier** - story text → `features/<slug>.feature` (3-7 Given/When/Then scenarios, user-observable only, no implementation terms) + `features/<slug>.qa.md` (numbered manual QA steps). Never writes code. 2. **coder** - feature file → unit tests + implementation