ql-verify

Enforce a 5-step verification gate for completion claims.

24|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/andyzengmath/quantum-loop --skill ql-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ql-verify
Source: https://github.com/andyzengmath/quantum-loop/tree/main/skills/ql-verify
Command: npx skills add https://github.com/andyzengmath/quantum-loop --skill ql-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Iron Law enforcement ensures that every completion claim is backed by fresh verification evidence, preventing confident but unverified results.

Core Features & Use Cases

  • 5-step gate function: IDENTIFY, RUN, READ, VERIFY, CLAIM.
  • Integration with /quantum-loop:execute for end-to-end verification and gate-guarded execution.
  • Standalone usage: can be invoked to verify any claim before marking work as done or committed.

Quick Start

Provide a claim to verify, and this skill will guide you through the five verification steps with fresh evidence.

Frequently Asked Questions about ql-verify

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

FAQPage Schema
How do I automate verification of completion claims before committing code?

The 5-step verification gate works by sequentially executing IDENTIFY, RUN, READ, VERIFY, and CLAIM. It enforces the Iron Law by requiring fresh evidence for any feature before allowing a completion claim to pass.

What is the Iron Law in software verification gates?

The Iron Law is a verification principle ensuring every completion claim is backed by fresh verification evidence. It prevents confident but unverified results from passing execution gates without proper proof.

Does the verification gate work with the quantum-loop workflow?

Yes, the verification gate integrates with /quantum-loop:execute for end-to-end verification and gate-guarded execution. It also supports standalone usage to verify any claim before marking work as done.

Can I use standalone claim verification without a full workflow system?

Yes, standalone usage allows you to verify any claim before marking work as done or committed. It provides safety guardrails and guides you through the five verification steps with fresh evidence independently.

What are the limitations of automated claim verification?

Automated claim verification requires fresh evidence for every completion claim, meaning you cannot reuse previous results. It applies specifically to features or stories needing verification before commits or passing gates.