bmad-build Skill (BMad Method) for Claude Code: Build Flow
Makes Claude take a story, feature or bug fix from plan to code to review and verification, for developers using BMad Method.
- Installs
- 14K
- on skills.sh
- Stars
- 54.9K
- on GitHub
- Files
- 14
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
bmad-build runs a fixed workflow. Claude clarifies your request, writes a plan file, implements it, reviews the diff and presents the result. A small change is built in the same session ("oneshot"). A larger one goes to a coding subagent ("full"). The default rule picks oneshot for roughly 100 changed lines or fewer.
The SKILL.md itself only runs one command: uv run --no-cache on _bmad/scripts/render_skill.py in your project, then it follows the workflow that script prints. If that script is missing, BMad is not set up yet. At the end it creates a local commit, and it never pushes on its own.
Good for
- Developers who hand Claude a ticket and want it built, reviewed and verified
- Teams using BMad Method planning artifacts and ticket files
- Anyone who wants a written plan and a review pass before a change is committed
Install bmad-build
Claude Code
- 1
Copy this prompt.
Install the bmad-build skill in Claude Code. Run this command: npx skills add bmad-code-org/BMAD-METHOD --skill '*' Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js and npm, Git, uv.
bmad-build only works in a project where BMad is set up, because it runs _bmad/scripts/render_skill.py from the project. The README says both routes need uv. The skills CLI route installs the full method, not this skill alone. This page describes the V7 preview file, and the README says V7 changes often.
From the project README. Source.
What's in the skill
When it loads
Implements a story, feature, or bug fix end to end: plan, code, review, verify. Use when the user hands one over and leaves the edits to you; a bare ticket id or 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.
Key facts
- Author
- bmad-code-org
- Repository
- bmad-code-org/bmad-method
- Installs on skills.sh
- 14,006 as of 2026-11-02
- License
- MIT (README)
- Last repo commit
- 2026-11-01
- skills.sh audits
- Gen Agent Trust Hub: pass; Socket: pass; Snyk: pass
What it includes
Runs uv run --no-cache on _bmad/scripts/render_skill.py
Run once from the project root with an optional --set workflow.route (oneshot or full) and --set workflow.review (none, quick or thorough). If the script is missing, Claude offers to set BMad up, and on any other failure it reports the output and stops.
Try: “bmad-build fix the pagination bug in the orders list, skip review”
Runs code ·
Render the workflowResolve the ticket or intent and check the git tree
Looks for an existing plan or ticket, ingests your request, and checks that the working tree is clean and the branch makes sense, halting to ask if not.
Read ·
Step 1: Clarify and routeWrite a plan file with acceptance criteria and a risk score
Writes the plan from a template with status, risk (low, medium or high), a code map and Given/When/Then acceptance criteria, and stops for your approval on full runs.
Write ·
Step 2: PlanCapture the baseline commit and hand off to a subagent
Records baseline_revision, sets the plan to in-progress, launches a no-context coding subagent that reads the plan, then writes a diff and runs the commands in the plan’s Verification section. SKILL rules say no push and no remote operations.
Runs code ·
Step 3: ImplementOne quick lens, or four thorough lenses, then triage
Quick runs one reviewer. Thorough runs Blind Hunter, Edge Case Hunter, Verification Gap Reviewer and Intent Alignment Auditor. Findings are logged in the plan and patched or deferred. Reviewers inspect only and do not modify code.
Write ·
Step 4: ReviewMark the plan built and make a local commit
If version control is available and the tree is dirty, it creates a local commit with a conventional message from the plan title. The rule is never to auto-push.
Runs code ·
Step 5: Presentcustomize.toml overrides for route, review, handoff and plan opening
Defaults can be overridden in _bmad/custom/bmad-build.toml. Settings include route, review, the implementation handoff, the review lenses and an open_plan command for your editor.
Customization
From the official docs
Permissions
Medium risk
The skill runs a script from your project, lets a subagent edit code, runs the plan’s verification commands and makes a local commit. Start from a clean branch so you can review the result.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It runs a script from your project folder
SKILL.md runs _bmad/scripts/render_skill.py with uv. That script comes from BMad setup in your project, so read it before you trust it. github.com
Subagents edit code and run commands
Step 3 hands the plan to a no-context subagent and runs the plan’s Verification commands. A plan’s commands are whatever it contains, so read the plan before you approve it. github.com
It makes a local commit
Step 5 commits locally with a message derived from the plan title and never pushes by itself. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | Ask for the review-only or plan-only parts yourself. The workflow has no read-only switch. |
|---|---|
| Talks to | None named in the skill files. Verification commands and installers can use the network |
| Sign-in and keys | No credentials are mentioned in the skill files. |
| Data retention | Plan files stay in your project. The diff file is written to the system temp directory. |
| Scopes |
|
Questions
What does bmad-build do?
It implements a story, feature or bug fix end to end: plan, code, review and verify. You hand over a request or ticket and it writes a plan, builds it, reviews the diff and presents the result.
How do I install it?
Use the install box above. The README documents a V7 preview route (skills CLI or plugin marketplace) and a stable v6.12 route (npx bmad-method install). After installing, ask the bmad skill to run bmad setup so the project gets its _bmad folder.
Why does it say BMad is not set up?
SKILL.md runs _bmad/scripts/render_skill.py from the nearest folder that contains _bmad/. If that file is missing, it offers to set BMad up with the bmad skill and then re-runs the command.
Does it commit or push my code?
It creates a local commit at the end when version control is available and the tree is dirty. step-05-present.md and the other steps say never to auto-push. It does not push unless you ask.
Can I skip the review?
Yes. SKILL.md says "skip review" or "no review" means review none. You can also ask for quick or thorough, and for the oneshot or full route.
Does it need an API key?
The skill files do not mention one. It needs uv, and the README lists Node.js 20.12 or newer and Python 3.10 or newer for the stable installer.
Is it safe?
It runs a script from your project, edits code through a subagent, runs the verification commands in its plan and makes a local commit. Use it on a clean git branch so you can review and undo the commit. The step files say not to push without being asked.
Information
updated Nov 2, 2026
- Repository
- bmad-code-org/bmad-method
- Folder
skills/bmad-build
Sources
Docs, issue trackers and discussions this page is built from.
Show all 8Hide
- BMAD-METHOD README · github.com
- bmad-build SKILL.md · github.com
- workflow.md · github.com
- customize.toml · github.com
- step-05-present.md · github.com
- step-03-implement.md · github.com
- step-04-review.md · github.com
- bmad-build SKILL.md · github.com