gsd-verifier

Cross-reference ROADMAP.md and REQUIREMENTS.md to generate VERIFICATION.md with gaps.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/cshyang/nochore --skill gsd-verifier-cshyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verifier
Source: https://github.com/cshyang/nochore/tree/main/capabilities/incubator/skills/gsd/agents/verifier
Command: npx skills add https://github.com/cshyang/nochore --skill gsd-verifier-cshyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that software development phases actually achieve their stated goals by enforcing a structured, automated verification workflow that checks observable truths, required artifacts, and key links, then reports findings.

Core Features & Use Cases

  • Automated phase-goal validation by cross-referencing ROADMAP.md and REQUIREMENTS.md.
  • Generates VERIFICATION.md with evidence, status, and optional gaps for human review.
  • Supports re-verification workflows and structured planning for phase improvements.

Quick Start

Run the verifier against a phase directory to generate a VERIFICATION.md.

Frequently Asked Questions about gsd-verifier

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

FAQPage Schema
How do I automate phase verification for software development goals?

Automated phase verification cross-references ROADMAP.md and REQUIREMENTS.md to determine must_haves, perform artifact and wiring checks across the project, and produce a VERIFICATION.md with gaps and human-verification notes.

What is phase verification in a codebase quality assurance workflow?

Phase verification in a codebase quality assurance workflow checks observable truths, required artifacts, and key links to validate that software development phases actually achieve their stated goals.

How do I check if required artifacts and wiring exist across my project?

You can check required artifacts and wiring by running an automated verifier that extracts must_haves from project requirements and performs structural checks across the codebase.

Can I generate a verification report with evidence and gaps for human review?

Yes, the verification process generates a VERIFICATION.md file containing evidence, status, and optional gaps specifically structured for human review and re-verification workflows.

Do I need ROADMAP.md and REQUIREMENTS.md to perform automated phase verification?

Yes, ROADMAP.md and REQUIREMENTS.md are required inputs because the automated phase verification process identifies phase goals and verification requirements directly from these files.

What's the best way to structure verification results for an orchestrator to plan re-verification?

The best way to structure verification results for an orchestrator is to generate a structured, machine-readable summary that includes phase status, gaps, and human-verification notes for automated planning.