GSD Verifier

Generate VERIFICATION.md with structured findings on specification gaps.

Updated Aug 7, 2025
One-click install
npx skills add https://github.com/hGriff0n/velopitt --skill gsd-verifier-hgriff0n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Verifier
Source: https://github.com/hGriff0n/velopitt/tree/main/.agent/skills/verifier
Command: npx skills add https://github.com/hGriff0n/velopitt --skill gsd-verifier-hgriff0n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures implemented work aligns with predefined specifications by generating a VERIFICATION.md containing structured findings, gaps, and evidence.

Core Features & Use Cases

  • Checks for previous VERIFICATION.md and evaluates gaps and re-verification needs.
  • Verifies must-haves, truths, artifacts, and key links across the project to ensure end-to-end traceability.
  • Produces a formal report with status, score, and optional human verification notes for audits.

Quick Start

Run the verifier against your repository to generate VERIFICATION.md and start phased evaluation.

Frequently Asked Questions about GSD Verifier

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

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

To verify code implementation against specifications, you can generate a VERIFICATION.md file containing structured findings, gaps, and evidence by loading context, establishing must-haves, and testing artifacts.

What is gaps analysis for software project requirement coverage?

Gaps analysis for requirement coverage identifies missing implementations by checking phase goals, plan alignment, and artifacts, producing a formal report with status, score, and evidence for audits.

How do I audit code quality and traceability for formal validation?

Audit code quality and traceability by validating key links, detecting anti-patterns, and verifying observable truths across the project, which produces a formal report with human verification notes.

Can I use automated verification to check previous audit reports?

Automated verification checks for previous VERIFICATION.md files, evaluates existing gaps, and determines re-verification needs to ensure current implementations still align with predefined specifications.

What are the limitations of automated specification verification?

Automated specification verification produces structured findings and scores but still requires human verification notes for audits, indicating that complete formal validation cannot be fully automated.