workflow-quality-gate — Pre-Release Go/No-Go

Degree of freedom: MIXED. Verdict and severity [HIGH freedom]; gate order, Critical pause, and report table [LOW freedom — run exactly].

Run before any production release. Each skill contributes a specific defect class. The combined result is a single verdict.

How to reason

1. Observe — what did each gate actually return?
2. Interpret — blocker vs recommended; plan-only fork vs apply-now
3. Classify — GO / GO WITH CONDITIONS / NO-GO
4. Severity — any Critical, or 2+ High without a named mitigation, is NO-GO

Worked example