bmad-validate-prd

Deprecated — forwards to bmad-prd (validate intent).

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/v6-shims/bmad-validate-prd/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clear, actionable deprecation shim with an explicit numbered activation workflow and concrete commands. Its only weakness is mild redundancy where the customization field list is repeated in both the deprecation notice and the handoff context.

Dimension	Reasoning	Score
Conciseness	The body is reasonably tight and avoids explaining concepts Claude already knows, but the deprecation notice and the pre-resolved customization bullet list repeat the same set of template field names twice, which could be tightened. It is mostly efficient but includes redundant restatement rather than being maximally lean.	2 / 3
Actionability	The body gives concrete, executable commands (the python3 resolve_customization.py invocation, the exact config.yaml path) and precise per-field instructions for forwarding intent and the four legacy fields. The guidance is copy-paste ready and unambiguous.	3 / 3
Workflow Clarity	The activation steps are explicitly numbered (1-4) with a clear sequence, and step 4 enumerates exactly what to pass to bmad-prd. The shim is a single forward with an explicit deprecation notice checkpoint and an explicit 'Do not execute any further steps' terminator, giving a clear, validated handoff.	3 / 3
Progressive Disclosure	No bundle files are present and the skill is under 50 lines with no need for external references. Per the rubric's simple-skill guidance, well-organized sections (overview, On Activation steps) earn a 3 with no external file references needed.	3 / 3
	Total	11 / 12 Passed

Description

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description accurately signals deprecation and a redirect to bmad-prd with validate intent, but it reads as an internal routing note rather than a user-facing trigger description. It lacks natural trigger terms and an explicit 'Use when' clause.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when validating an existing PRD or reviewing a product requirements document for completeness.'

Replace internal jargon ('forwards to bmad-prd (validate intent)') with user-facing language such as 'Validates an existing product requirements document (PRD); use when checking a PRD for completeness and consistency.'

Include common natural terms users would say ('validate a PRD', 'review a product requirements document') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ('forwards to bmad-prd') and a concrete intent ('validate intent'), but it does not list multiple specific actions; it is essentially a single redirect statement. It is more concrete than 'Helps with documents' (score 1) but far less comprehensive than the score-3 multi-action example, so it lands at 2.	2 / 3
Completeness	It states what the skill does (forwards to bmad-prd with validate intent) but provides no 'Use when...' clause or explicit trigger guidance, so the 'when' is only implied. Per the rubric, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	The text uses internal/jargon terms ('forwards to bmad-prd', 'validate intent') rather than natural phrases a user would actually say. A user would not naturally invoke 'forwards to bmad-prd', and there is no coverage of common user-facing trigger terms like 'validate a PRD' or 'check a product requirements document'.	1 / 3
Distinctiveness Conflict Risk	Naming a specific target skill (bmad-prd) gives it a clear niche and low conflict risk, but the phrase 'forwards to bmad-prd (validate intent)' is terse and does not surface distinct user-facing triggers, leaving it somewhat overlapping with bmad-prd itself rather than fully distinct.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bmad-code-org/BMAD-METHOD
Path: src/bmm-skills/v6-shims/bmad-validate-prd/SKILL.md
Commit: bb45db4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.