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.