spec-verifier

Extract requirements from spec files and verify implementation evidence with glob and grep.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/GavinTPA/ai-powerhouse-starter --skill spec-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-verifier
Source: https://github.com/GavinTPA/ai-powerhouse-starter/tree/main/my-skills/spec-verifier
Command: npx skills add https://github.com/GavinTPA/ai-powerhouse-starter --skill spec-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically verifies that completed work matches the original specification so teams stop guessing whether promised features and criteria were actually delivered. It reduces manual re-reading of specs, prevents missed requirements, and produces evidence-based results for release decisions.

Core Features & Use Cases

  • Requirements extraction: Reads spec files (SKILL.md, plans, README sections) and extracts discrete, checkable requirements.
  • Severity classification: Tags requirements as Blocker, Should-Have, or Nice-to-Have based on signal words and section context.
  • Evidence search and reporting: Searches implementation scope with glob/grep, classifies each requirement as Met/Partial/Missing, captures file/line evidence, and generates a timestamped Spec Compliance Report.
  • Auto-save and traceability: Saves reports to the target's docs/verification folder and links into daily notes to build a verification history.
  • Use case: QA or engineering teams verifying a skill, feature, or repository against its plan before shipping.

Quick Start

Run the spec-verifier against the chosen spec file and implementation folder to produce a saved spec compliance report.

Frequently Asked Questions about spec-verifier

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

FAQPage Schema
How do I verify code implementation against original specifications?

To verify code implementation against original specifications, this tool extracts discrete requirements from spec files and searches your repository for evidence using glob and grep, classifying each requirement as Met, Partial, or Missing to produce a compliance report.

What is spec verification and how does severity classification work?

Spec verification systematically checks completed work against original specifications. Severity classification tags extracted requirements as Blocker, Should-Have, or Nice-to-Have based on signal words and section context to prioritize compliance gaps.

How do I generate a compliance report for a project repository before shipping?

Generate a compliance report by running verification against your chosen spec file and implementation folder. It captures file and line evidence for each requirement and auto-saves a timestamped Spec Compliance Report to the target's docs/verification folder.

Can I verify documentation and plan artifacts instead of just code?

Yes, you can verify documentation and plan artifacts. The tool is applicable to code, documentation, and plan artifacts when checking implementation folders, skill packages, or project repositories against their original spec files.

Does spec verification work without external dependencies or components?

Yes, spec verification works without external dependencies or components. It operates independently to read spec files like SKILL.md, plans, or README sections, searching the implementation scope natively to build evidence-based results.

What is the best way to prevent missed requirements during code review?

The best way to prevent missed requirements during code review is to automate extraction of discrete, checkable requirements from spec files and search repositories for evidence, preventing manual re-reading errors and producing evidence-based results for release decisions.