CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-build

Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An exceptionally lean launcher: one exact command, precisely resolved placeholders, enumerated flag values, and explicit failure handling for every anticipated outcome. The only structural gap is that the bundle's two reference files are not surfaced from the body.

DimensionReasoningScore

Conciseness

A ~20-line body with zero padding: "Run the following command exactly once without changing the current working directory" states constraints in a single clause, and no line explains concepts Claude already knows. Every token is operational, matching the lean 5 anchor.

5 / 5

Actionability

Fully executable: a copy-paste-ready bash command with precisely defined placeholders ("the nearest folder containing `_bmad/`, from the working directory upward"), enumerated flag values (`oneshot` or `full`; `none`, `quick`, or `thorough`), and explicit fallback behavior for every anticipated case.

5 / 5

Workflow Clarity

A simple skill whose single action is unambiguous, with explicit validation checkpoints: `HALT: <reason>` → "report the reason and stop"; missing script → offer setup and rerun; "On any other output or failure... report the command output and stop." No destructive or batch operations apply a cap.

5 / 5

Progressive Disclosure

The launcher body is minimal and well organized, but scoring against the actual bundle structure, the two reference files (references/claims-check.md, references/deletion-check.md) are never referenced or signaled from the body — a minor navigation gap that keeps it below the 5 anchor's well-signaled references.

4 / 5

Total

19

/

20

Passed

Description

78%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.

A well-structured description with an explicit 'Use when' clause, concrete trigger objects, clear skip conditions, and correct third-person voice. Its main weakness is specificity — the core action is stated abstractly rather than as an enumerated list of concrete capabilities, and a few natural trigger phrasings are absent.

Suggestions

Replace the abstract "Turns implementation work into working code, reviewed and verified" with enumerated concrete actions, e.g. "Implements features and bug fixes from a delegated story or issue, then runs edge-case review and verification passes on the result."

Add natural phrasings users actually say — "implement", "build", "ticket", "task" — alongside the existing "feature, story, bug fix, issue link" triggers.

Briefly state what "reviewed and verified" concretely means (e.g. claims and deletion review passes) to further distinguish the skill from generic code-review skills.

DimensionReasoningScore

Specificity

Names the domain and actions ("Turns implementation work into working code, reviewed and verified"), but the verbs stay abstract — concreteness comes from scope lists ("feature, story, bug fix") rather than several enumerated capabilities. It falls below the 4 anchor, which requires several specific concrete actions like "extracts text, fills forms, converts pages".

3 / 5

Completeness

Explicitly answers both what ("Turns implementation work into working code, reviewed and verified") and when ("Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts") with concrete trigger phrases, plus explicit skip conditions. Clearly matches the 5 anchor rather than 4, whose 'when' is less specific.

5 / 5

Trigger Term Quality

Good natural-term coverage: "delegates a feature, story, bug fix", "a bare story or issue link counts", and "Explicit BMAD requests always qualify" include synonyms users would naturally say. Not 5 because common phrasings like "implement", "build this", or "ticket" are missing.

4 / 5

Distinctiveness Conflict Risk

The BMAD framing and "Explicit BMAD requests always qualify" carve a distinct niche, and exclusion clauses ("Do not volunteer for user-directed interactive edits...") reduce conflict. Overlap risk remains with generic coding and code-review skills for triggers like "bug fix" or "meaningful change", so it does not reach the minimal-conflict 5 anchor.

4 / 5

Total

16

/

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-build/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.