ai Output Quality Gate 1

Never accept AI-generated work on vibes. This skill runs any artifact — code, a document, a research brief, a plan, a dataset — through a structured acceptance gate: inventory the claims, demand evidence for each, attack the weak points adversarially, and return a verdict. It catches the failures that slip past a casual read: fabricated facts, untested code, plans with missing steps, confident nonsense.

• An agent just delivered work and you need to decide: accept it, or send it back.

• You are about to ship, publish, or present something an AI produced.

• You want a repeatable QA bar for agent output across a team or workflow.

• For line-by-line code review of a diff — use a dedicated code reviewer instead. The gate checks whether the work meets its brief; it does not replace domain review.

• When you wrote the work yourself and know it is correct. The gate is for work you did not produce.

Write down, in one paragraph, what the artifact was supposed to do. If the original request is available, quote it. If not, reconstruct it from context and label it reconstructed-brief. A gate without a brief is just criticism — the brief is the standard.