CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-prd

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A tightly engineered, highly actionable facilitation skill with clear multi-step sequencing, explicit validation gates, and well-signaled one-level-deep references. Its single weakness is conciseness: the full memlog command is repeated verbatim multiple times and several parenthetical caveats could be consolidated.

Suggestions

Define the memlog append/init command signature once (e.g. in a Conventions block) and refer to it by name thereafter, instead of spelling out the full `uv run .../memlog.py append --workspace ... --type ... --text ...` line three times.

Collapse qualifying parentheticals (e.g. "two or three turns, not ten", "that is intake, not the dump") into tighter inline notes or move them to a reference, preserving the directive without the chatter.

Consider moving the detailed On Activation step list or the Reviewer Gate mechanics into a reference file, keeping SKILL.md as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explaining what a PRD is), but it spells the full `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type ... --text ...` command verbatim several times instead of defining it once, and carries qualification clauses that could be tightened — the "mostly efficient but could be tighter" anchor rather than the fully lean one.

2 / 3

Actionability

Provides exact commands (memlog.py append/init, resolve_customization.py), concrete file roles, explicit frontmatter fields (title, status, created, updated), and named entry points — fully copy-paste-ready guidance matching the executable-instruction anchor.

3 / 3

Workflow Clarity

Sequenced end-to-end (Activation 1-5 → Intent Modes → Discovery order → Reviewer Gate → Finalize 1-8) with explicit validation checkpoints (confirm activation steps ran, "Resolve before polish", polish-last rationale, memlog audit) and feedback loops, matching the clear-sequence-with-explicit-validation anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview that defers detail to clearly signaled one-level-deep references ("follow `references/headless.md`", "Load `references/validate.md`", "uses the prompt and output format in `references/validate.md`"), all of which exist as real files, rather than inlining that material — matching the well-signaled-one-level-deep anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A concise, third-person description that pairs concrete actions (create/update/validate) with an explicit "Use when" trigger clause, cleanly answering both what and when. Its only soft spot is that all actions share the single object "PRD", so the action vocabulary is somewhat narrower than the best examples.

DimensionReasoningScore

Specificity

Names three concrete actions on a concrete object ("Create, update, or validate a PRD"), matching the multiple-specific-actions anchor rather than the single-domain partial anchor at 2.

3 / 3

Completeness

Explicitly answers both what ("Create, update, or validate a PRD") and when ("Use when the user wants help producing, editing, or validating a PRD"), satisfying the explicit-trigger anchor at the top level.

3 / 3

Trigger Term Quality

"Use when the user wants help producing, editing, or validating a PRD" supplies natural verb variations (produce/edit/validate) plus the keyword "PRD" a user would actually say; not downgraded to 2 because the verb cluster gives good natural coverage.

3 / 3

Distinctiveness Conflict Risk

PRD authorship is a clear niche with distinct create/update/validate triggers, making overlap with other skills unlikely; matches the clear-niche anchor rather than the could-overlap anchor at 2.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.