🛡️ Gauntlet Loop — Bounded Multi-Agent Quality Improvement Loop

A deterministic, bounded quality improvement loop that eliminates infinite token burns, self-grading delusions, and regression churn. Deploys an unyielding, 4-role protocol (Freeze → Build → Fresh Critic → Automated Gate → Integrator) with hard mathematically enforced termination boundaries, OWASP security header verification, and multi-viewport visual regression gates.

When to Use

Trigger Conditions

Execute this skill when:

1. Multi-Round Code/Doc Refinement: A complex task requires iterative quality improvement across multiple passes.
2. Preventing Self-Grading Delusion: The builder agent must NOT evaluate its own output; an isolated Fresh Critic must score the work against frozen criteria.
3. Web Application Hardening Gate: Iterating on web apps, frontend templates, or API servers requiring strict security headers (CSP, HSTS) and responsive viewport checks (375px, 768px, 1280px).
4. Hard Stop Boundaries Required: Guarding against runaway agent loops where changes oscillate or degrade previous passes.
5. Mission-Critical Delivery: High-stakes deliverables requiring an ironclad ACCEPTANCE_PACKET.md.