superspec:verify

Load specs, map scenarios to tests, and report coverage gaps.

3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superspec:verify
Source: https://github.com/HankLiu447/SuperSpec/tree/main/skills/verify
Command: npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Verify Skill ensures that implementation aligns with specifications by validating that every Requirement has a corresponding test and every Scenario has a test, preventing drift and unverified changes.

Core Features & Use Cases

  • Load specs from superspec/changes/[id]/specs and parse all Requirements and Scenarios.
  • Map each Scenario to an existing test, detect missing tests, and identify extras not covered by specs.
  • Generate a comprehensive verification report detailing coverage, gaps, and actionable recommendations.
  • Enforce pre-archive checks to ensure code readiness and traceability between specs, tests, and implementations.

Quick Start

Run superspec verify <change-id> to perform a verification pass before archiving.

Frequently Asked Questions about superspec:verify

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

FAQPage Schema
How do I verify code matches specs before archiving?

Missing tests during spec verification indicate a coverage gap where a scenario lacks a corresponding test. The deterministic workflow detects these missing tests, identifies extra tests not covered by specs, and flags them in the verification report before archiving.

What is requirements traceability and when do I need it for archiving?

Requirements traceability for archiving is the process of mapping every requirement and scenario to a corresponding test to prevent drift. You need it before archiving to enforce pre-archive checks and confirm that implementation aligns with specifications.

How do I check test coverage for specification scenarios?

You can check test coverage for specification scenarios by loading specs, parsing all requirements and scenarios, matching each scenario to an existing test, and generating a comprehensive verification report detailing coverage, gaps, and actionable recommendations.

Why does unverified code drift from specifications?

Unverified code drifts from specifications when changes are implemented without validating that every requirement has a corresponding test. Running a pre-archive verification pass prevents drift by quantifying gaps and ensuring traceability between specs, tests, and implementations.

What's the best way to identify gaps between specs and implemented code?

The best way to identify gaps between specs and implemented code is to apply a deterministic workflow that loads specs, extracts requirements and scenarios, matches them to tests, and reports coverage issues and actionable recommendations for archiving readiness.