---

name: legion-verify-spec description: Verify an identified spec or intent against actual behavior and evidence. Use for requested sign-off or requirement coverage, not routine tests after every edit. A verification-only request is read-only. metadata: source-skill: verify-spec source-sha256: "e4c31ea95bc71553bc9b41220fdde00f9cee5fbad07e094dbce6d4162397d6fc" edition: "2026-09-06"

Verify Spec

Verify the promised reality, not the amount of code or the confidence of a completion report.

Resolve the document from the user's path, name, or current conversation. Follow the project's established location when needed. Ask which document only when multiple plausible targets remain and the choice changes the review; absent command arguments alone do not justify a question.

Read the complete governing document and identify its requirements. For each, choose the evidence that can actually establish it: source and call paths, focused tests, runtime behavior, rendered artifacts, or lived judgment. Reuse valid existing evidence with its date and limits; do not substitute a passing build for a behavioral claim or rerun unrelated suites for ceremony.

Report each requirement as:

• PASS: the relevant evidence establishes the requirement.
• FAIL: evidence demonstrates missing or wrong behavior.
• PARTIAL: a specific part is established and another required part remains incomplete.
• UNVERIFIED: the necessary evidence is absent or the relevant judgment has not occurred. Uncertainty is not automatically a demonstrated defect.

Include precise evidence pointers and state the unresolved consequence. Machine checks cannot decide whether the experience feels right to the person or whether a student understands.

A review-only request does not authorize editing the spec, moving it, appending a log, fixing code, or changing live state. Return the verdict. If the same request already includes implementation or repair, continue that authorized work and reverify without requesting permission again. During an authorized closure, follow the repository's established artifact lifecycle.