bmad-review-verification-gap

Forwards review requests to the bmad-review skill with the verification-gap lens.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-review-verification-gap-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-verification-gap
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-review-verification-gap
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-review-verification-gap-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for users who previously invoked a dedicated verification-gap review, redirecting them to the consolidated bmad-review skill without breaking existing workflows. ## Core Features & Use Cases - Deprecated Forwarding: Routes all requests to the bmad-review skill using only the verification-gap lens. - Consistent Output Format: Presents markdown rendering only, listing any gap_shape "other" findings under an Other findings heading. - Use Case: When a user or automation still calls the old verification-gap review, this Skill ensures the request is handled by the unified bmad-review skill and returns either findings or the exact line "No verification gaps found." ## Quick Start Ask the assistant to run a verification-gap review on your content and it will forward the request to bmad-review with the verification-gap lens.

Frequently Asked Questions about bmad-review-verification-gap

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

FAQPage Schema
How do I run a verification-gap review now that this skill is deprecated?

Invoke the bmad-review skill directly on your content and specify the verification-gap lens. This deprecated skill simply forwards your request there, so calling bmad-review yourself achieves the same result.

What output does the verification-gap review produce?

It produces a markdown rendering only, with no JSON block. Findings with gap_shape "other" are listed under an Other findings heading, and when nothing is found it outputs exactly "No verification gaps found."

Is bmad-review-verification-gap still maintained?

No, it is deprecated and merged into bmad-review. It remains only as a forwarding shim so existing references continue to work, and new usage should target bmad-review directly.

When should I not use this deprecated forwarding skill?

Avoid it when setting up new workflows or documentation, since it adds an unnecessary indirection layer. Use bmad-review with the verification-gap lens for full control over lenses and output options.