gsd-validate-phase

Validate implemented code against SPEC.md and REQUIREMENTS.md, generating a VALIDATION.md report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that implemented code and configurations align with the defined SPEC and REQUIREMENTS, surfacing deviations before release.

Core Features & Use Cases

  • Cross-checks implementation against SPEC.md and REQUIREMENTS.md to identify gaps and confirm coverage.
  • Generate a VALIDATION.md report detailing coverage, gaps, and a gate status to drive quality decisions.
  • Suitable for post-implementation reviews in software, infrastructure, and integration projects to ensure conformity and traceability.

Quick Start

Run a validation pass against SPEC.md and REQUIREMENTS.md to ensure alignment and generate a VALIDATION.md report.

Frequently Asked Questions about gsd-validate-phase

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

FAQPage Schema
How do I validate that my code implementation matches the project spec?

To validate code implementation against your spec, run a post-implementation review that cross-checks your code and configurations against defined SPEC and REQUIREMENTS documents, generating a detailed report on coverage and deviations.

What is a spec validation report and what does it include?

A spec validation report details implementation coverage and gaps by cross-checking code against SPEC and REQUIREMENTS. It includes alignment details, identified deviations, and a PASS or FAIL gate status to drive quality decisions before release.

How do I perform a post-implementation review for infrastructure projects?

Perform a post-implementation review for infrastructure projects by running a validation pass against SPEC and REQUIREMENTS documents to confirm conformity and traceability, surfacing any configuration deviations before release.

When do I need to verify requirements coverage before release?

You need to verify requirements coverage before release when you want to ensure implemented code and configurations align with defined SPEC and REQUIREMENTS, surfacing any gaps or deviations to drive final quality decisions.

Does the validation process work for software and integration projects?

Yes, the validation process works for software, infrastructure, and integration projects. It confirms alignment with the SPEC and REQUIREMENTS during post-implementation reviews, ensuring conformity and traceability across different project types.

What's the best way to surface code deviations from defined requirements?

The best way to surface code deviations is to cross-check the implementation against SPEC and REQUIREMENTS documents. This generates a VALIDATION.md report detailing coverage gaps and a gate status to drive quality decisions.