gsd-verify

Execute verification steps from PLAN.md and generate VERIFICATION.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute verification steps from PLAN.md and generate VERIFICATION.md to validate progress and gate completion.

Core Features & Use Cases

  • Read the "Verification steps" section from PLAN.md to determine acceptance criteria.
  • Execute each verification step, record results, and create VERIFICATION.md for auditing.
  • Enforce gating by requiring all steps to pass before marking the phase complete.

Quick Start

Run gsd-verify to read PLAN.md, execute each verification step, and generate VERIFICATION.md.

Frequently Asked Questions about gsd-verify

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

FAQPage Schema
How do I verify project plan steps and generate verification documentation?

To verify project plan steps, you can execute verification criteria from PLAN.md and generate a VERIFICATION.md file under the .planning directory to audit and validate progress. This ensures each step is validated before marking completion.

What are quality gates in software engineering and how do they gate phase completion?

Quality gates are validation checkpoints that enforce phase completion by requiring all verification steps to pass. They read acceptance criteria from PLAN.md, execute them, and prevent progress until every step is successfully validated and recorded.

How do I enforce acceptance criteria compliance from a project plan?

You can enforce acceptance criteria compliance by reading the verification steps section from PLAN.md, executing each step sequentially, and withholding phase completion status until all criteria pass and are recorded in VERIFICATION.md for auditing.

Do I need a PLAN.md file to verify software engineering project progress?

Yes, a PLAN.md file is required. The verification process reads PLAN.md to determine acceptance criteria, executes the specified verification steps, and outputs the results into VERIFICATION.md to gate and validate your project progress.

What is the best way to audit and record software verification step results?

The best way to audit verification step results is to execute each step from PLAN.md and automatically generate a VERIFICATION.md file under the .planning directory, creating a persistent record of passed and failed validation gates for compliance.

Why does my project phase not mark as complete after running verification steps?

Your project phase remains incomplete because the verification process enforces strict gating. It requires all verification steps from PLAN.md to pass before allowing phase completion, recording any failures in VERIFICATION.md to block progress.