anti-hallucination-gates

Require concrete artifacts as evidence before declaring completion across verification gates.

14|Updated May 28, 2026
One-click install
npx skills add https://github.com/Redtropig/harness-anchor --skill anti-hallucination-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-hallucination-gates
Source: https://github.com/Redtropig/harness-anchor/tree/main/skills/anti-hallucination-gates
Command: npx skills add https://github.com/Redtropig/harness-anchor --skill anti-hallucination-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use before claiming "done", "fixed", "complete", or "passing". Default-FAIL contract — every criterion needs evidence; express uncertainty if missing.

Core Features & Use Cases

  • Enforces evidence-backed completion before declaring success across builds, tests, and handoffs.
  • Guides how to collect and present artifacts that prove criteria are met.
  • Applies across verification, feature progress, and craft handoffs to ensure traceability.

Quick Start

Collect concrete artifacts that prove each criterion before declaring completion.

Frequently Asked Questions about anti-hallucination-gates

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

FAQPage Schema
How do I prevent premature completion claims during software builds?

Prevent premature completion by applying evidence-backed gating during build verification, requiring concrete artifacts that prove every criterion is met before declaring success.

What is an artifact-evidence contract for verification gates?

An artifact-evidence contract is a default-FAIL mechanism for verification gates requiring concrete corroborating artifacts for each criterion, enforcing traceable and safety-conscious evaluation across builds and tests.

How do I require proof of criteria before declaring a feature complete?

To require proof before declaring a feature complete, collect concrete artifacts that corroborate each progress criterion, expressing uncertainty if any required evidence is missing.

Does evidence-backed gating work for craft handoffs and traceability?

Yes, evidence-backed gating applies across craft handoffs to ensure traceability by enforcing that every handoff criterion has corroborating artifacts before the transfer is considered complete.

What happens if artifacts are missing when verifying tests and builds?

If artifacts are missing during verification, the system enforces a default-FAIL contract, requiring you to express uncertainty rather than allowing claims of being fixed, passing, or complete.