spec-verify-output

Verify LiveSpec command run artifacts against expectations contracts.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-verify-output-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-verify-output
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-verify-output
Command: npx skills add https://github.com/julien-m/livespec --skill spec-verify-output-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running a LiveSpec slash command, there is no built-in way to confirm the run actually behaved as specified. This Skill checks a command's recorded run artifact against its expectations contract and reports success, drift, blocked, or error outcomes. ## Core Features & Use Cases - Artifact Verification: Compares the latest .specs/.runs/<command>-*.json artifact against the command's expectations.md contract using must, may, and must_not rules. - Outcome Reporting: Surfaces success, drift, error, or blocked outcomes exactly as reported by the livespec verify-output CLI, with optional JSON envelope output. - Preview Mode: Renders a Markdown verification report without a run artifact, optionally saving it to .specs/.previews/. - Use Case: After running /spec-specify in CI, invoke /spec-verify-output specify to confirm the run passed all contract rules and exit with code 0 before merging. ## Quick Start Ask the assistant to run /spec-verify-output for the specify command to check its latest run artifact against its expectations contract.

Frequently Asked Questions about spec-verify-output

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

FAQPage Schema
How do I verify a LiveSpec command run artifact?

Run /spec-verify-output followed by the command name, such as /spec-verify-output specify. It locates the latest .specs/.runs artifact, checks it against the command's expectations.md contract, and reports success, drift, blocked, or error.

What do the verify-output exit codes mean?

Exit code 0 means success with all must rules passing, 1 means drift where at least one must rule failed but the run exited 0, and 2 means blocked due to a missing precondition or artifact.

Can I verify output without a run artifact?

Yes, use the --preview flag to skip artifact resolution and render a Markdown report from the expectations demo section. Add --save to write the report to .specs/.previews/.

Why does verify-output report blocked?

Blocked occurs when the target command never ran so no artifact exists, the expectations file is missing, or an override file is malformed. Run the target command first, then re-verify.

Does spec-verify-output modify project files?

No, it is read-only by default and forbidden from touching src/ or .specs/. The only exception is the --preview --save mode, which writes a report to .specs/.previews/.