quality-gate

Red-team artifacts iteratively and track weighted scores to detect stagnation.

10|2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/raddue/crucible --skill quality-gate-raddue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/raddue/crucible/tree/main/skills/quality-gate
Command: npx skills add https://github.com/raddue/crucible --skill quality-gate-raddue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the quality and robustness of various artifacts (designs, plans, code, etc.) by subjecting them to rigorous, iterative adversarial review until they meet a high standard or stagnation is detected.

Core Features & Use Cases

  • Iterative Red-Teaming: Continuously challenges artifacts with adversarial testing.
  • Stagnation Detection: Prevents endless loops by identifying when no meaningful progress is being made.
  • Weighted Scoring: Uses a defined scoring system (Fatal=3, Significant=1) to track progress objectively.
  • Use Case: Before deploying new code, run it through the quality gate to catch potential bugs, security vulnerabilities, and design flaws that might have been missed in initial reviews.

Quick Start

Use the quality-gate skill to red-team the attached design document.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How does iterative red-teaming improve code review and artifact quality?

Stagnation detection prevents endless review loops by identifying when no meaningful progress is being made during artifact revision, using weighted scoring to track objective progress and escalating to the user upon hitting limits or architectural concerns.

Can I run quality assurance red-teaming on design documents and implementation plans?

Weighted scoring tracks quality assurance progress objectively by assigning defined values to findings, with Fatal issues scoring 3 and Significant issues scoring 1, ensuring measurable evaluation of artifact improvements during adversarial review.

How do I perform quality gating on a design document before deployment?

Quality gating escalates to the user when adversarial review hits iteration limits or detects architectural concerns, ensuring that critical design flaws, potential bugs, and security vulnerabilities are surfaced for human intervention rather than automatically dismissed.

What are the limitations of automated stagnation detection during artifact review?

The limitation of automated stagnation detection is that it may escalate to the user when iteration limits are hit or architectural concerns arise, meaning complex design flaws might require manual intervention rather than being resolved through automated adversarial review loops.