Playbooks · Coding tasks
BMad v7 is a preview, not the stable release: what changes, and whether to try it before it ships
Written October 31, 2026
For a BMad user searching "bmad v7": v7 is preview alpha on the main branch of the BMad Method repository, the stable line is v6.12, and trying the preview means accepting breaking changes between updates. If the project has to keep working, stay on v6.12.
Two lines, one repository
BMad ships on two lines, and the repository's own front page says so plainly. The stable release is v6.12, installed by the npm installer and frozen aside from bug fixes. V7 is in preview alpha on the main branch: its skills, install path, and docs change often. Both routes need uv for BMad setup and Python scripts. The repository gives a release estimate of mid-November 2026 for v7 and adds that it might be sooner; the preview label is the fact that matters, not the date. A preview that is still described as preview alpha is not a release, whatever the estimate said.
The stable install, for Node.js 20.12+ and Python 3.10+, is the command most BMad users already know:
npx bmad-method install
The v6.12 source and documentation live on the V6.12 branch of the same repository. The preview install is a different path. You need an AI coding tool that supports skills. With Node.js, npm, and Git, the preview installs as two modules, one command each:
npx skills add bmad-code-org/BMAD-METHOD/skills/core-tools --skill '*'npx skills add bmad-code-org/BMAD-METHOD/skills/method --skill '*'
Each command installs one module whole. Core tools hold the bmad skill for setup and help, so every install needs them. Open your coding tool in the project and ask the bmad skill to run bmad setup, then invoke bmad-build with what you want to change. Asking for bmad status shows versions and what to run next; bmad setup installs updates — it runs npx skills update, refreshes the project, and cleans up renamed and removed skills.
What the preview changes
The direction of v7 was presented in the BMad Code livestream of 16 October 2026 with Tim Dickey. Three changes in that presentation matter to anyone with a v6 project. First, each epic gets its own folder, with an epic file that works as the spec, and each story is built when it is next rather than written up front with all the others. Second, big planning documents become folders of small, well-named files, with one primary file per output, so a change touches one small file instead of a long document. Third, the sprint-planning.yaml file goes away. The presentation also puts the epic at about 7 to 11 stories, as one developer's unit of work, with initiatives above epics and stories below them.
Those are presented changes, not installed behavior you can rely on yet. The repository warns that preview skills, the install path, and the docs change often, and recommends the preview only for solo developers or small teams that can pivot as things change before beta. An overview of the repository's preview material also notes setup glitches and Windows path issues. Treat every v7 detail as provisional: read the repository's front page again on the day you install, because the detail you memorized may already have moved.
Whether to try it
Stay on v6.12 if the project has a deadline, a team, or a shared setup that others depend on. The stable line exists for exactly that case, and the repository recommends it when stability is needed until v7 is finalized. The preview earns its place in one situation: a solo developer or a small team, on work that can absorb rework, who wants to learn the new shape early and can change direction when an update breaks something.
If you try it, keep it separate. Do not install the preview into a v6.12 project you are mid-way through, and do not mix preview and stable installs across a team. Try it in a copy of a project, or in a throwaway project, with the v6.12 install untouched. Expect to redo setup steps after updates, and expect skill names and file layouts to shift. When something breaks, the repository points preview problems to GitHub Issues or the BMad Discord. A preview that costs a morning of rework on a throwaway project is a cheap lesson; the same breakage inside a live project is not.
What to do instead, on v6.12
Nothing about the preview changes what v6.12 does today. If the job in front of you is agreeing what to build, or starting work on a codebase you inherited, the stable line already covers it, and the pages below use it. The preview becomes the right choice when it ships as a stable release with documentation that stops changing under you — until then, it is a look ahead, not an upgrade.
Related playbooks
- Move a v6 BMad project to the v7 preview
- Auggie 0.37.0: first release after the takeover
- Agree what to build before building it: write a short product requirements document with BMad
- Qwen4-Max Preview: 14 days, then it retires
Sources
- https://github.com/bmad-code-org/BMAD-METHOD
- https://docs.bmad-method.org/start/build-your-first-change/
- https://www.youtube.com/watch?v=LHQbLmKJWDs
- https://www.youtube.com/watch?v=uH5R6RpHDn0
Back to: Coding playbooks hub · Also: BMad Method, the stable install · Write a short product requirements document with BMad · Start work on a codebase you inherited