spec-verify

Map codebase entrypoints, branches, and tests to spec entries and generate coverage reports.

Updated Feb 20, 2026

Search Tags:#reporting #verify #entrypoints #branch-coverage #spec-coverage #test-to-spec

Ready to run

npx skills add https://github.com/sergseven/agent-dev --skill spec-verify-sergseven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-verify
Source: https://github.com/sergseven/agent-dev/tree/main/suites/reverse-spec/skills/spec-verify
Command: npx skills add https://github.com/sergseven/agent-dev --skill spec-verify-sergseven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the verification of your repository's specification coverage, helping teams confirm that generated specs align with the codebase and reveal gaps before release.

Core Features & Use Cases

Entrypoint coverage: Detects public entrypoints in the codebase and checks them against spec files.
Branch coverage: Analyzes domain/service logic branches to ensure corresponding spec scenarios exist.
Test-to-spec mapping: Maps tests to spec criteria to surface unmapped tests.
Deep-gap analysis (optional): Performs a deep gap analysis by prompting deeper review of domain specs to surface ambiguities.
Report generation: Outputs spec/.reverse-spec-coverage.md with an overall result and per-pass details.
Use Case: Before releasing a feature, run this skill to validate that tests and specs comprehensively describe intended behavior.

Quick Start

Run the reverse-spec spec-verify skill against your repository to generate the coverage report.

Frequently Asked Questions about spec-verify

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

FAQPage Schema

How do I verify that my specs fully cover my codebase?▼

Spec coverage verification maps public entrypoints, business-logic branches, and tests to corresponding spec entries. It classifies results as PASS or NEEDS_WORK based on predefined criteria, generating a structured markdown report with actionable remediation guidance.

What is reverse spec coverage and when do I need it?▼

Reverse spec coverage automates the validation of specification alignment before a feature release. You need it when you want to confirm that generated specs accurately describe intended behavior and surface gaps between your tests, codebase, and documentation.

How do I check test-to-spec mapping for unmapped tests?▼

Test-to-spec mapping analyzes your test suite and matches tests to spec criteria to surface unmapped tests. The process applies a 70% mapping threshold to classify results and outputs a detailed remediation report.

What are the pass criteria for branch and entrypoint coverage analysis?▼

Branch coverage analysis requires 75% of domain logic branches to have corresponding spec scenarios, while entrypoint coverage requires 80% of public entrypoints to be mapped to spec entries to achieve a PASS classification.

Can I perform a deep gap analysis on domain specs?▼

Yes, optional deep-gap analysis prompts a deeper review of domain specs to surface ambiguities. This supplements the standard entrypoint, branch, and test coverage checks by identifying unclear specification definitions.

What limitations exist when automating specification coverage reports?▼

The automated reporting relies on fixed pass thresholds of 80% entrypoint, 75% branch, and 70% test-to-spec coverage. It outputs a static markdown file and cannot dynamically adjust criteria or integrate external testing frameworks beyond the repository scan.