verify

Verify completed Belmont tasks against acceptance criteria and coding standards.

4|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/blake-simpson/belmont --skill verify-blake-simpson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/blake-simpson/belmont/tree/main/plugin/skills/verify
Command: npx skills add https://github.com/blake-simpson/belmont --skill verify-blake-simpson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates comprehensive verification and code review of completed Belmont tasks to ensure that implementations meet acceptance criteria and coding standards.

Core Features & Use Cases

  • Reads PRD.md, TECH_PLAN.md, and archived MILESTONE-*.done.md to gather acceptance criteria, design references, and context.
  • Dispatches verification and code-review sub-agents to validate functionality, design fidelity, and PRD alignment.
  • Generates a structured verification report and records follow-up tasks in PROGRESS.md when issues are found.

Quick Start

Invoke /belmont:verify to start a full verification and code-review pass for completed tasks.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate code review and verification against acceptance criteria for completed tasks?

Automated verification reads PRD.md, TECH_PLAN.md, and archived MILESTONE-*.done.md files to dispatch verification and code-review sub-agents, ensuring implementations meet acceptance criteria and coding standards.

Can I use this to generate a structured verification report and update progress tracking?

Yes, the verification process generates a structured report of its findings and automatically updates PROGRESS.md with results, creating follow-up tasks for any detected issues to track resolution.

How does end-to-end verification work with design references and PRD alignment?

End-to-end verification dispatches sub-agents to validate functionality, design fidelity, and PRD alignment by gathering context and design references from archived milestone files and planning documents.

Do I need archived MILESTONE-*.done.md files to run a full verification pass?

Yes, archived MILESTONE-*.done.md files are required inputs alongside PRD.md and TECH_PLAN.md to provide the acceptance criteria and design references needed for comprehensive task verification.

What's the best way to validate completed Belmont tasks for coding standards compliance?

The best way to validate coding standards compliance is dispatching automated code-review sub-agents that check completed tasks against established criteria, returning a structured report of any deviations found.