CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

91%

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

100%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 exemplary lean launcher: fully executable, with clear conditional handling, explicit error-recovery and halt checkpoints, and no token waste. It defers detail to a rendered workflow rather than inlining it, fitting the progressive-disclosure ideal for a simple skill.

DimensionReasoningScore

Conciseness

Lean ~12-line launcher with zero concept explanation or padding; every line is actionable instruction and assumes Claude's competence, so every token earns its place.

5 / 5

Actionability

Provides a fully executable copy-paste command with explicit placeholder substitution and concrete flag-append rules for routes and review selections, covering the common cases.

5 / 5

Workflow Clarity

Single unambiguous action with explicit conditional branches and checkpoints: success -> follow printed workflow.md, missing file -> run setup then re-run (feedback loop), other failure -> report and HALT.

5 / 5

Progressive Disclosure

Under-50-line well-organized body that defers all detail to a rendered one-level workflow.md; no nested references and no inlined walls of text, satisfying the simple-skill exception.

5 / 5

Total

20

/

20

Passed

Description

83%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-crafted description that clearly states what the skill does and when to use it, with concrete triggers and thoughtful exclusions. It is specific, third-person, and low-conflict, falling just short of top marks only on action exhaustiveness and trigger synonym coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('working code, reviewed and verified') plus concrete trigger/exclusion scenarios (feature, story, bug fix, ignore-file, typo-only); short of a fully exhaustive action list so not a 5.

4 / 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...') with concrete trigger phrases and clear exclusions.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('feature, story, bug fix, or meaningful change', 'bare story or issue link') that users would actually say; 'BMAD' is jargon and a few common synonyms are absent, so just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche via the BMAD context, reviewed-and-verified framing, and explicit exclusions (mechanical maintenance, interactive edits, VC ops); broad 'feature/story/bug fix' triggers leave minor overlap risk with general coding skills.

4 / 5

Total

17

/

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.

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.