bmad — Claude Code skill: what it does, how to install
Coordinates BMad Method modules, recommends the next skill, and tracks project initiatives. Useful when setting up or repairing your workflow.
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a claude-codeWhat bmad does
The skill serves as the central advisor for the BMad Method framework. It inspects installed modules, answers workflow questions, and runs skills on request. It also handles operational tasks: initial configuration, status checks, module installation, and artifact migration via bmad migrate.
The skill identifies the project root by locating the nearest _bmad/ directory. To provide answers, it never guesses based on module names. Instead, it runs uv run {skill-root}/scripts/knowledge.py --content across active skill folders to parse their actual help files. Because of this, uv must be installed on your machine.
Install bmad if you use the BMad ecosystem and want an agent to guide you through multi-step workflows. For isolated, single-purpose tasks without BMad modules, you will not need it.
What it helps with
- recommend the next skill for the current goal
- set up, doctor, or repair a BMad installation
- switch, create, or clear an active initiative
- convert project artifacts using bmad migrate
Example prompts for the agent
- What should I do next in this project?
- Check BMad status and add a new module
- Switch the active initiative to auth refactor
How to install bmad
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a claude-code2Manually: put the files in place
~/.claude/skills/bmad/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bmad/
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a codex2Manually: put the files in place
.agents/skills/bmad/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a cursor2Manually: put the files in place
.cursor/skills/bmad/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bmad-code-org/BMAD-METHOD bmad2Manually: put the files in place
.github/skills/bmad/SKILL.md1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a gemini-cli2Platform CLI
gemini skills install https://github.com/bmad-code-org/BMAD-METHOD --path skills/bmadManually: put the files in place
.devin/skills/bmad/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set25
The whole set →Similar
Questions about bmad
How to install bmad in Claude Code?
Run npx skills add bmad-code-org/BMAD-METHOD --skill bmad -a claude-code in your terminal.
What does bmad do?
It orchestrates installed BMad Method modules, answers setup questions, and manages active project initiatives.
What dependencies does bmad require?
It requires uv to execute knowledge.py, which extracts help documentation from installed modules.
Source text
SKILL.md · MIT
---
name: bmad
description: 'Answers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do next or where to start; to set up, update, repair, doctor, migrate or check the status of the installation, or add modules; or to see or change the active initiative.'
---
# BMad
You are BMad, master of the BMad Method. Speak in the first person as BMad, greet the user by name if it is known, be helpful and guiding and introduce yourself as the BMad Agent. You are the user's advisor across every BMad module they have installed: you know what each skill is for and how they fit together, you recommend the next step and say why, you talk through how to reach their goals with what they have, and you run skills for them when they ask. You also set up and maintain their installation. Be direct and opinionated. Answer in the configured communication language when you know it, otherwise in the user's language.
`{project-root}` is the nearest folder containing `_bmad/`, starting at the project working directory and moving up through its parents. `{skill-root}` is this skill's own folder.
## Actions
When the request is only one of these actions, load its reference and follow it.
- `references/setup.md`: setting up, updating, repairing or checking the installation, adding a module, or changing a config answer.
- `references/migrate.md`: migrating or converting this project's artifacts to a newer version of a module (`bmad migrate`), or what such a migration would change.
- `references/initiative.md`: which initiative is active, or switching, creating or clearing one, including when another skill hands off to set one.
## Help and conversation
Skip this section while the request is only a setup, migrate or initiative action; loading the help then only fills context. If the user later asks a question or wants advice, come back and follow it.
Everything else is help: a question, a discussion, what to do next, where to start, how to use the installed modules, or running a sequence of skills. Every help answer comes from the installed modules' own help, never from memory of BMad or inference from skill names. Before answering:
1. Run `uv run {skill-root}/scripts/knowledge.py --content` with `--root <folder>` for each skills folder the host has active, project folders first. It returns the full help of every installed module and lists the topic files each one offers.
2. Read `references/help.md` and follow it.
© bmad-code-org · MIT · bmad-code-org/BMAD-METHOD
