Individual skill

ql-verify

Part of the quantum-loop autonomous development pipeline (brainstorm → spec → plan → execute → review → verify). Iron Law verification gate. Requires fresh evidence before any completion claim. Use before claiming work is done, before committing, or before marking a story as passed. Triggers on: verify, check, prove it works, ql-verify.

skills/ql-verify/SKILL.md

Read pinned source

Source commit bed463b5db7ec57e30f3c3a47ca1025f95cfe453

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 24
Repository last updated: Jun 25, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agentskills Repository topic
claude-code Repository topic
claude-code-plugin Repository topic
skillsmp Repository topic
claude-code-skill Repository topic
legal Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 8,854 bytes

Read excerpt


# Quantum-Loop: Verify

## Inline-vs-adversarial review split (P5.A7 / US-007)

The verify gate distinguishes **routine** checks (deterministic verdict, exit-code 0/non-0) from **adversarial** checks (require judgement) and routes them differently:

| Check kind | Examples | Mode | Rationale |
|---|---|---|---|
| Routine | typecheck, lint, full test suite, file-org conventions | **inline-only** in implementer prompt before STORY_PASSED | Verdict is deterministic; subagent round-trip adds 25min for zero signal value |
| Adversarial | cross-story file conflicts, intent drift vs PRD, security review, architecture / API-shape | **subagent dispatch** (spec-reviewer, quality-reviewer, security-reviewer, architect) | Requires judgement, context, and human-readable explanation that grep cannot provide |

Routine checks emit literal tokens the orchestrator greps for evidence:
- `[INLINE-REVIEW] typecheck OK`
- `[INLINE-REVIEW] lint OK`