verify

Validates intent, plan, and execution artifacts against sources before phase transitions.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill verify-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/allemaar/open-skills/tree/main/skills/verify
Command: npx skills add https://github.com/allemaar/open-skills --skill verify-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work can drift from its original goal, and an agent's self-report of having checked something is not proof. This Skill acts as a formal phase gate that compares the intent, plan, and execution artifacts against each other and actively re-checks every load-bearing claim against its source before you proceed. ## Core Features & Use Cases - Three-artifact drift check: Compares the original intent, the plan, and the actual execution, citing specific evidence for any gaps, drifts, or issues found. - Active per-claim source re-check: Re-opens the source for every load-bearing factual claim, including checking the committed blob or built artifact rather than the mutable working tree. - Structured verdict output: Produces a verdict with clean, gaps, drifts, issues, and a status of clean, gaps-found, plan-not-found, incomplete, or unverified, plus routing to the next step. - Use Case: Before merging a feature branch, run the gate to confirm the committed code actually matches the plan and intent, catching cases where the working tree looks fine but the committed HEAD is broken. ## Quick Start Run /verify to check whether my intent, plan, and execution still align before I move to the next phase.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify that executed work matches the original plan?

Run the /verify gate, which compares the intent, plan, and execution artifacts against each other and cites specific evidence for any drift, skipped steps, or unplanned changes. It returns a structured verdict with a status such as clean, gaps-found, or incomplete.

What is the difference between verify, double-check, and reflect?

Verify is the formal gate checking intent, plan, and execution artifacts with active source re-checks. Double-check is a quick re-read of a single claim, and reflect is an informal pause with no artifact requirement or gate.

What happens if there is no plan when running verify?

The plan is optional. When absent, verify skips the plan and execution comparison checks and reports a status of plan-not-found rather than failing, while intent and execution remain hard requirements.

Why does verify re-check claims against committed code instead of the working tree?

A dirty working tree or stale build can pass a claim while the committed HEAD or shipped artifact is broken. Verify checks the consumed form, such as the committed blob via git show or the built dist, unless uncommitted work is itself the artifact under verification.

Can an agent's self-report count as verification evidence?

No. An agent reporting that it already checked something is not evidence. Verify requires a fresh read of the source for every load-bearing claim, and any claim not re-checked is reported as unverified.