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.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Run the following command exactly once without changing the current working directory.
Replace {project-root} with the nearest folder containing _bmad/, from the working directory upward.
Replace {skill-root} with the absolute path to this skill's directory.
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"- When the invocation names a route (
oneshotorfull), append--set workflow.route=<value>to the command. - When the invocation names a review selection (
none,quick, orthorough; "skip review" or "no review" meannone), append--set workflow.review=<value>to the command. - The command prints the skill's workflow: follow it.
HALT: <reason>: report the reason and stop. - If the script does not exist, BMad is not set up in this project yet. Offer to set it up using
bmadskill, then run the command again. If you do not have thebmadskill, offer to install it first. - On any other output or failure, including
uvbeing unavailable, report the command output and stop. Do not run any workflow source directly.
- Repository
bmad-code-org/BMAD-METHOD
- Revision
61e01f8
- Last updated
- First committed
Also appears in
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.