CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-validate-prd

Deprecated — forwards to bmad-prd (validate intent)

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

78%Weight 40%Scale 1-5

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 tight, highly actionable activation workflow with concrete commands and an explicit handoff, well-suited to a single-purpose forwarding shim. Its main weakness is redundancy — the customization field list and migration guidance are repeated — which inflates token cost without adding clarity.

Suggestions

Define the four legacy customization fields once and reference them by name in the notice and step 4 instead of re-enumerating them each time.

Add a brief verification that resolve_customization.py returned a value before emitting the deprecation notice and forwarding.

Consider shortening the deprecation notice by moving the full migration field list to a single canonical location.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the legacy customization field list is enumerated three times (intro, deprecation notice, step 4) and the long notice restates migration guidance already implied, fitting 'mostly efficient but could be tightened' rather than the lean score-4 anchor.

3 / 5

Actionability

Step 1 gives a copy-paste command ('uv run .../resolve_customization.py --skill ... --key workflow'), step 2 names exact config files, step 3 supplies verbatim notice text, and step 4 specifies the exact intent, four legacy fields, and verbatim user input to forward — fully actionable guidance.

5 / 5

Workflow Clarity

A clear numbered 1–4 sequence with an explicit handoff checkpoint ('bmad-prd takes the workflow from here. Do not execute any further steps') is present, but there is no verification that step 1's customization resolution succeeded before proceeding, a minor validation gap that fits score 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle directories exist and the skill is under 50 lines with a single well-organized 'On Activation' section and no nested reference chains, so under the simple-skill exception progressive disclosure scores 5 on structure alone.

5 / 5

Total

17

/

20

Passed

Description

46%Weight 40%Scale 1-5

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 is specific and accurate about being a deprecated forwarding shim, but it lacks any trigger guidance ('when to use') and carries only one natural keyword. It is clear on 'what' yet silent on 'when', which caps its completeness.

Suggestions

Add a 'Use when...' clause naming the natural trigger (e.g., 'Use when a user asks to validate a PRD and invokes bmad-validate-prd by name').

Surface the keyword 'PRD' in the description itself, not only in the skill name, to improve trigger-term coverage.

Clarify that this is a compatibility shim retained for legacy invocations, so users know to prefer bmad-prd directly.

DimensionReasoningScore

Specificity

The phrase 'forwards to bmad-prd (validate intent)' names one concrete action (forwarding) with a specific target skill and intent, matching the '1-2 concrete actions but not comprehensive' anchor rather than the generic score-2 anchor or the multi-action score-4 anchor.

3 / 5

Completeness

It clearly states what it does ('forwards to bmad-prd' with validate intent) but provides no 'Use when...' or equivalent trigger guidance, so per the cap it cannot exceed 3 and matches the 'clear what, missing when' anchor.

3 / 5

Trigger Term Quality

Only 'validate' is a natural user keyword; the description omits 'PRD' and any trigger phrase, fitting 'one or two generic keywords; missing the natural phrases users say' rather than the broader coverage at score 3.

2 / 5

Distinctiveness Conflict Risk

Naming the specific consolidated skill 'bmad-prd' and the PRD-validation niche gives it a mostly-distinct identity with only minor overlap risk against that closely related skill, fitting the score-4 anchor rather than the broader score-3.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bmad-code-org/BMAD-METHOD
Reviewed

Table of Contents

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.