gsd-verify

Goal-backward verification validates implemented features against stated phase goals by tracing requirements to code, tests, and documentation, orchestrating UAT, and generating a VERIFICATION.md report with auditable evidence to prevent false completion positives.

Goal-backward verification is a validation process that confirms built features actually achieve stated project goals by mapping requirements backward to code and artifacts, structuring UAT, and recording verdicts, gaps, and recommended fixes in a VERIFICATION.md report.

You map requirements to code and tests by running verification workflows that export and wire checks, orchestrate user acceptance testing, and generate structured documentation providing auditable evidence of phase goal alignment and requirement fulfillment.

The verification workflow relies on internal subagents like verifier and integration-checker to perform modular quality checks, and requires no external dependencies to map requirements, orchestrate UAT, and produce the final VERIFICATION.md evidence report.

Generating auditable UAT artifacts is best achieved by structuring user-facing tests to confirm real-world usability, wiring checks to codebase features, and documenting verdicts, evidence, and gaps within a structured VERIFICATION.md report.

You need a VERIFICATION.md report when completing a development phase to provide auditable evidence that e2e and integration testing align with requirements, recording validation verdicts, identified gaps, and recommended fixes to guarantee goal-aligned verification.