spec-verify

Verify specifications against test results using the spec-test tool.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Varuas37/spec-test --skill spec-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-verify
Source: https://github.com/Varuas37/spec-test/tree/main/src/spec_test/skills/spec-verify
Command: npx skills add https://github.com/Varuas37/spec-test --skill spec-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven verification helps teams ensure that the implemented tests accurately reflect formal specifications, reducing drift and late-stage defects.

Core Features & Use Cases

  • End-to-end verification: Runs spec-test verification to compare design/specs against tests and reports gaps.
  • Issue-driven debugging: Identifies failing specs and guides updates to tests or implementations.
  • CI/CD readiness: Integrates into pipelines to keep specs green across deployments.

Quick Start

Install the spec-test package (e.g., pip install spec-test), then run spec-test verify to scan your specs and tests. The tool will produce a report summarizing PASS, FAIL, PENDING, and SKIP statuses and guide you to fix issues.

Frequently Asked Questions about spec-verify

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

FAQPage Schema
How do I verify specs against test results in a CI/CD pipeline?

Spec verification in a CI/CD pipeline automates the comparison of design/specs against tests to identify failing specs and report gaps. The process produces a report summarizing PASS, FAIL, PENDING, and SKIP statuses to guide fixes across deployments.

What is spec-driven verification and how does it identify failing tests?

Spec-driven verification ensures implemented tests accurately reflect formal specifications by comparing design/specs against tests. It identifies failing specs by scanning tests with @spec decorators and generating a status report to guide updates to tests or implementations.

Do I need the spec-test tool installed to run spec verification?

Yes, spec verification requires the spec-test tool to be installed. You must install the package via pip install spec-test, ensure specs are located in design/specs, and have tests discoverable in tests with @spec decorators to run the verification process.

Can I use spec verification for debugging failing tests?

Yes, spec verification supports issue-driven debugging by identifying failing specs and guiding updates to tests or implementations. It compares design/specs against test results to pinpoint exactly where gaps or drift exist, reducing late-stage defects during development.

What is the best way to check if my tests accurately reflect formal specifications?

The best way to check if tests reflect formal specifications is running spec-test verify to scan your specs and tests. This automated verification produces a detailed report of PASS, FAIL, PENDING, and SKIP statuses to highlight any gaps or drift.

Why does spec verification fail to discover my tests during a scan?

Spec verification fails to discover tests when requirements are unmet. Tests must be located in the tests directory and explicitly use @spec decorators, while formal specs must be placed in the design/specs directory for the spec-test tool to successfully find and verify them.