Skills bmad-code-org bmad-method BMad Method
bmad
- Use it when:
- You start BMad in a project, want to update or repair it, or wonder which BMad skill to run next.
- It does:
- Creates and maintains the project's _bmad/ folder, and answers questions only from the installed modules' own help, never from memory.
- You get:
- A working BMad setup, an active initiative once you pick or create one, and a recommended next skill with the reason; it can run that skill for you.
- Speaks as:
- BMad, a direct, opinionated advisor who introduces itself as the BMad Agent.
- Needs:
- uv; updates run npx skills update.
Skill 1 of 24 in the BMad Method bundle, before bmad-agent-analyst.
Only works inside its bundle: Sets up and advises on the other BMad skills: its setup and help work from the modules and skills installed beside it, so alone it has nothing to set up, answer from or recommend. Install BMad Method instead.
Needs uv. Run its setup first: every other BMad skill runs scripts from the _bmad/ folder it creates.
TL;DR
The hub of the BMad Method. Every other BMad skill runs scripts from the project's _bmad/ folder and sends you here when it's missing. Setup creates that folder with uv and asks each installed module's configuration questions; on later runs the same flow checks each module's version, runs npx skills update, and offers to remove retired skills, duplicate copies and leftovers of a v6 install, always asking before it deletes anything. It can also migrate a project's documents to a newer version of a module, following a plan you approve first. Work is grouped into initiatives, a folder per body of work under the output folder, and the skill shows, switches, creates or clears the active one. Everything else is help: where the project stands, which installed skill comes next and why, or the trade-offs of an approach, all taken from the help files the installed modules ship. When one skill is the clear next step it suggests running it in a fresh context, offers to run it here; asked for a sequence of skills, it runs them one at a time, checking each result with you.
Summarizes the skill at e734d3a.
npx skills add https://github.com/bmad-code-org/bmad-method --skill bmad skills.sh pageSource on GitHubAll skills from bmad-code-org/bmad-method
- Total Downloads
- 16,600 on skills.sh, Nov 9, 2026
- Repo stars
- 55,140 bmad-code-org/bmad-method
- First seen
- Sep 5, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 1,021 |
| Sep 28 | 1,428 |
| Oct 5 | 2,827 |
| Oct 12 | 3,166 |
| Oct 19 | 1,777 |
| Oct 26 | 1,889 |
| Nov 2 | 1,623 |
| Nov 9 | 1,683 |
| Category |
Find, write, vet and route to other skills. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
One-time configuration or scaffolding of a project, account or tool. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From bmad-code-org/bmad-method at e734d3a. Checked daily, last changed Nov 6, 2026.
Frontmatter
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:
- Run
uv run {skill-root}/scripts/knowledge.py --contentwith--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. - Read
references/help.mdand follow it.