Validate implemented work against phase goals using empirical evidence.
npx skills add https://github.com/getdatasurge/fresh-staged --skill gsd-verifier
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
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.
Run the verifier from the project root to produce VERIFICATION.md with a structured findings report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
apsulliValidates implemented code against phase requirements using empirical evidence checks.
nickthelegendValidate implemented work against phase goals and generate a VERIFICATION.md report.
JustineDevsEnforce Test-Driven Development by requiring failing tests before production code.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
