gsd-validate

Validate code against SPEC.md and REQUIREMENTS.md to produce a PASS/FAIL report.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-validate
Source: https://github.com/alo-exp/silver-bullet/tree/main/skills/gsd-validate
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the implementation aligns with SPEC.md and REQUIREMENTS.md to prevent drift between code and intent.

Core Features & Use Cases

  • Cross-check implementations against SPEC.md to ensure traceability
  • Verify REQUIREMENTS.md coverage and generate a gap report
  • Produce a formal Validation Report detailing PASS or remediation steps

Quick Start

Validate that implementation matches the spec by cross-checking SPEC.md and REQUIREMENTS.md, then generate a PASS/FAIL report.

Frequently Asked Questions about gsd-validate

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

FAQPage Schema
How do I verify my implementation matches the software requirements spec?

Validate implementation against specs by cross-checking code, tests, and documentation against SPEC.md and REQUIREMENTS.md to confirm coverage, traceability, and compliance for each requirement ID.

What is requirements traceability and when do I need to check it?

Requirements traceability links each REQ-ID to implemented code and tests to prevent drift. You need to check it when ensuring your build fulfills every formal specification before release.

How do I generate a validation report for software quality gates?

Generate a validation report by applying compliance checks across files and tests, which produces a formal PASS confirmation or documents specific gaps and remediation steps for your quality gates.

Can I use this to check REQUIREMENTS.md coverage without external dependencies?

Yes, you can verify REQUIREMENTS.md coverage without external dependencies because the validation process runs standalone, applying checks across your existing files and tests to output a formal gap report.

What is the best way to prevent drift between code and formal specifications?

The best way to prevent code and spec drift is to run validation checks cross-referencing implementations against SPEC.md and REQUIREMENTS.md, producing a detailed gap report with necessary remediation steps.

What happens when implemented code fails to meet the SPEC.md requirements?

When code fails to meet SPEC.md requirements, the validation process documents the specific gaps in coverage and traceability, outputting a formal report with detailed remediation steps to achieve compliance.