CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-prd

The earlier PRD workflow, kept for comparison with John the Product Manager (bmad-agent-pm), who now coaches PRDs. Use when the user names bmad-prd; otherwise use John.

Quality

73%

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 ./skills/bmad-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-engineered orchestration document: an explicitly ordered activation → discovery → finalize pipeline with concrete commands, exact file conventions, fallback paths for every failure mode, and genuine validation gates. Content is dense and appropriately split across one-level-deep references and assets, with only minor tightening and asset-path indirection worth addressing.

DimensionReasoningScore

Conciseness

The body is dense, operational prose that assumes Claude's competence — no basic concepts (what a PRD is, what elicitation means) are explained, and nearly every sentence carries instructions. Minor instances could be trimmed (the full `memlog.py append` command is spelled out multiple times; the Conventions 'File roles' bullet runs very long), matching 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean-every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete, executable guidance throughout: copy-paste-ready `uv run .../memlog.py append --workspace ... --type <decision|change|override|assumption|event>` commands with flags, exact output paths (`prd-{slug}/prd-{slug}.md`), specific frontmatter fields (title, status, created, updated), and fallback install commands (`npx skills add bmad-code-org/BMAD-METHOD --skill bmad`). Minor gaps keep it at 4: several steps depend on `{workflow.*}` placeholders resolved externally, and facilitation steps like 'greet the user' are necessarily open-ended.

4 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with ordering rationale ('Brain dump → Stakes calibration → Working mode → mode-scoped work'; 'Polish goes last so it does not redo work after reviewer fixes'), and Finalize is a numbered 1–8 sequence with explicit validation checkpoints (memlog audit, input reconciliation before polish, reviewer pass, open-item triage). Error-recovery feedback loops are present: script-not-found → offer setup → rerun, and missing `.memlog.md` → init plus a bootstrap subagent — matching 'clear sequence with explicit validation steps; feedback loops for error recovery'. No destructive/batch-operation cap applies to this document-authoring skill.

5 / 5

Progressive Disclosure

References are well-signaled at the point of need (`references/validate.md` for the Validate intent and rubric-walker prompt, `references/headless.md` for headless runs) and both are real, one-level-deep files verified in the bundle — headless.md points onward only to `assets/headless-schemas.md`, with no nested chains. Heavy detail (validation pipeline, headless procedure, templates, checklist) is appropriately split out of SKILL.md. The minor gap keeping it at 4 rather than 5: the four `assets/` files (prd-template.md, prd-validation-checklist.md, validation-report-template.html, headless-schemas.md) are reachable only through `{workflow.prd_template}`-style placeholder indirection rather than direct paths in the body.

4 / 5

Total

17

/

20

Passed

Description

52%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 works well as a deprecation/redirect notice — it is highly distinctive and explicitly routes users to the successor skill — but it does not describe what the skill itself does (create/edit/validate PRDs), leaving the 'what' vague. Its trigger guidance is narrow and explicit but limited to the skill's own name, missing natural PRD-related phrasings.

Suggestions

State the skill's actual capabilities in the description, e.g. 'Creates, edits, and validates PRDs through a facilitated coaching workflow' — the current text never says what the skill does, only that it is the 'earlier PRD workflow'.

Add natural trigger phrasings beyond the skill's own name, such as 'product requirements document', 'write a PRD', or 'draft a PRD', while keeping the narrow 'use when the user names bmad-prd' routing rule.

Briefly note the key difference from John (bmad-agent-pm) — e.g. what this workflow does differently — so users choosing between them have a basis for comparison rather than only a redirect.

DimensionReasoningScore

Specificity

The description names the domain ("The earlier PRD workflow, kept for comparison with John the Product Manager") but never states concrete actions the skill performs (e.g., create, edit, or validate PRDs), matching the anchor 'names the domain but actions are minimal or generic'. It is above 1 because the domain and purpose are identified, and below 3 because no specific actions of this skill are listed.

2 / 5

Completeness

The 'when' is explicit and concrete ("Use when the user names bmad-prd; otherwise use John") but the 'what' is thin — "The earlier PRD workflow" never says what the skill actually does. This sits between anchor 2 (vague what, no when) and anchor 4 (both present, when could be more explicit): the explicit when lifts it above 2, and the vague what caps it below 4.

3 / 5

Trigger Term Quality

Relevant keywords are present ("PRD", "bmad-prd", "bmad-agent-pm", "coaches PRDs") but common natural variations users would say — "product requirements document", "write a PRD", "product spec" — are missing, matching 'some relevant keywords but missing common variations or synonyms'. It does not reach 4 because keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

"Use when the user names bmad-prd; otherwise use John" gives a clear niche trigger (the skill's own name) and explicitly resolves the conflict with its closest sibling (bmad-agent-pm), matching 'clear niche with distinct triggers; minimal conflict risk'. It is above 4 because the main overlap risk is disambiguated within the description itself.

5 / 5

Total

13

/

20

Passed

Validation

100%

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

skills/bmad-prd/SKILL.md

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.