GSD Verifier

Name: GSD Verifier
Availability: InStock
Author: dataSURGE

Validate implemented work against phase goals using empirical evidence.

Updated Jan 24, 2026

Search Tags:#specification #verification #quality-assurance #verify #gaps #stubs #empirical-evidence

Ready to run

npx skills add https://github.com/getdatasurge/fresh-staged --skill gsd-verifier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: GSD Verifier
Source: https://github.com/getdatasurge/fresh-staged/tree/main/.agent/skills/verifier
Command: npx skills add https://github.com/getdatasurge/fresh-staged --skill gsd-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that implemented work satisfies phase goals by checking for presence of must-haves, proper artifacts, and correct wiring against the project ROADMAP and phase PLANs, producing structured evidence.

Core Features & Use Cases

Verify must-haves are present and correctly implemented across code, tests, and docs.
Detect stubs, placeholders, and incomplete implementations, and report gaps.
Generate VERIFICATION.md with a concise, machine-readable and human-readable report of findings.
Use during quality assurance or pre-release validation to ensure alignment with phase goals.

Quick Start

Run the verifier from the project root to produce VERIFICATION.md with a structured findings report.

Frequently Asked Questions about GSD Verifier

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

FAQPage Schema

How do I empirically verify implemented work against project specifications?▼

To empirically verify implemented work against specifications, validate that code, tests, and documentation meet phase goals by checking for must-haves, proper artifacts, and intact wiring to produce structured evidence rather than relying on claims.

How do I detect stubs and incomplete implementations during software verification?▼

Detect stubs and incomplete implementations during software verification by scanning the codebase for placeholders and gaps, validating that artifacts are substantive, and reporting findings in a structured, machine-readable VERIFICATION.md report.

What is empirical evidence-based specification verification for quality assurance?▼

Empirical evidence-based specification verification for quality assurance is the process of substantiating artifacts and checking wiring integrity against ROADMAP and phase PLANs, ensuring must-haves are present and correctly implemented.

Can I use phase-based verification to check wire integrity and artifact substantiation across code and tests?▼

Yes, phase-based verification checks wire integrity and artifact substantiation across code, tests, and documentation, ensuring implemented work meets phase goals and generating a structured findings report for quality assurance.

What is the best way to document software verification findings for pre-release validation?▼

The best way to document software verification findings for pre-release validation is to generate a concise, machine-readable and human-readable VERIFICATION.md report detailing presence of must-haves, detected gaps, and artifact substantiation.

Why does my software verification report claims instead of empirical evidence of completed work?▼

Software verification reports claims instead of empirical evidence when validation skips checking for substantive artifacts and intact wiring against phase PLANs, a gap solved by enforcing must-have presence and generating structured proof of findings.