Murat K Ozcan
423690c3d7
* fix(skills): activation preflight checks required skills only against roots the caller names resolve_customization.py accepts repeated --root, in precedence order, and passes them to setup_check. Without roots, setup_check no longer claims a required skill or the module record is missing or outdated, since it cannot see the host's other active roots. Notes that need no root order stay. * fix(skills): report a tag-pinned install as pinned with the re-add command A module whose skills-lock entry carries a ref was reported newer-available, but npx skills update keeps the pin and cannot apply the newer version. Status now reports pinned with the command that adds the module again at the newer tag. * fix(skills): tickets find rejects a bare number that would fall back to the backlog With no folder, a bare number the initiative does not resolve was taken from the backlog file carrying that id. It now errors as ambiguous and lists the candidates. * fix(skills): preflight reads the record that wins the ordered roots and survives an unreadable file render_skill.py takes --root like the resolver. * fix(skills): only a version-tag ref counts as a pin A branch or commit ref is followed by npx skills update, so it stays newer-available. * fix(skills): a numeric tracker id still finds its backlog ticket and the bare-number error names the real case * fix(skills): pinned re-add command covers one scope; test the renderer preflight and pinned status The re-add command lists only the skills in the module record's scope. The renderer tests install setup_check and cover --root forwarding. Status tests cover pinned as a settled state. * fix(skills): a numeric tracker id wins over a backlog ticket's local id * feat(skills): build loads any run folder that names its ticket and container step-01 of bmad-build and bmad-build-auto reads the main document of any <type>-*/ run folder in the initiative or the ticket's epic folder whose ticket and container match. A document without container keeps the research rule. A loaded document that lists test files makes the plan include the work that turns them green. * feat(skills): retrospective gathers the epic's run folders and companions * fix(skills): migration rewrites a module config path that moves with the planning folder * fix(skills): match a run's container by the folder find names, carry test work into oneshot plans, align companions and the migration check * fix(skills): mirror leaves a bare number out of the backlog, and a pin needs the lock entry to name the module's repository * fix(skills): match a run's container by its last folder name and have the build run the listed tests * docs: describe v7 module install and the three-file config model * docs: mark the plugin marketplace route not v7-ready * docs(skills): core-tools help names how to add the Test Architect * docs: list external modules that restate the ticket tree rules * fix(skills): bmad-customize points to bmad-toolsmith for custom skills * docs: align the config and module pages with setup behavior * docs: call team settings defaults a personal file can override, and note single-skill modules * fix(skills): no re-add command for an untagged pre-release, and the backlog help names the tracker id exception * fix(skills): listed tests get a Verification command that blocks completion, and the migration rewrites each layer that holds the moved path * fix(skills): a released pinned module from a non-GitHub source says to re-add it from its source * fix(skills): bmad-build runs the plan's Verification commands before review * fix(skills): bmad-customize recommends bmad-toolsmith only when installed
4.5 KiB
title, description, sidebar
| title | description | sidebar | ||
|---|---|---|---|---|
| Add Modules | Add a module with the Skills CLI and bmad setup, keep it updated, and find out where to build your own. |
|
A module is a set of skills that belong together, plus a bmod-<code> record folder that tells the bmad skill about them. You add one with the Skills CLI, then run bmad setup <code> to configure it. There is no separate installer, registry, or build step.
:::note[Using v6.12?]
v6.12 adds modules through npx bmad-method install, with --custom-source for Git URLs and local paths. That flow is documented on the V6.12 branch and summarized at the end of this page.
:::
Official modules
| Module | What it adds | Source |
|---|---|---|
Test Architect (TEA), code tea |
Test strategy, automation, test review, traceability, and release-gate decisions through an agent and eight workflows | bmad-method-test-architecture-enterprise |
Creative Intelligence Suite, code cis |
Brainstorming, design thinking, and problem-solving agents | bmad-module-creative-intelligence-suite |
Game Dev Studio, code gds |
Game design documents and game-aware planning for Unity, Unreal, Godot, and custom engines | bmad-module-game-dev-studio |
Each repository's README says which BMad version it supports. TEA's bmad-tea-automate generates heavier test coverage than the built-in bmad-qa-generate-e2e-tests; Test Completed Work helps you choose between them.
Add a module
From your project folder, add the module's skills with the Skills CLI. For TEA:
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise
Select your coding tool and the skills you want. Include the module record, bmod-tea here. Keep the project and global installation scopes consistent with the rest of your BMad skills.
Then ask the bmad skill to run bmad setup tea. Setup asks the module's configuration questions, places its scripts under _bmad/<code>/, and offers any migration the module ships. Ask for bmad status to confirm the module and its version.
Any repository that follows the module layout installs the same way. The source can be a local folder, or a repository at a tag, as in owner/repo#v1.2.0.
Keep a module updated
bmad setup compares each module's version with its source and offers to run npx skills update when a newer one exists. If you update by hand, run bmad setup afterwards.
When a newer version exists for a module installed from a tag, bmad status reports pinned, because npx skills update keeps it on that tag. It also gives the npx skills add owner/repo#<tag> --skill … command that moves the module record and its skills to the newer tag.
Create your own module
Ask Smithy, the bmad-toolsmith skill, to scaffold a module, add skills and agents to it, and validate it. Toolsmith describes what it builds and how.
A module needs a bmod-<code> record folder holding a bmod.toml, a stub SKILL.md, and a help/help.md that bmad reads to guide users. Each of its skills carries a small bmod.toml that names the record. A module of one skill needs no record folder: that skill's own bmod.toml holds both tables. Publish the repository and others add it with npx skills add. To test before publishing, add it from the local folder.
Modules in v6.12
v6.12 reads modules from the official list in npx bmad-method install, or from a Git URL or local path you give it:
| Input | Example |
|---|---|
| HTTPS or SSH Git URL | https://github.com/org/repo, git@github.com:org/repo.git |
URL with a subfolder or @ref |
https://github.com/org/repo/tree/main/my-module, https://github.com/org/repo@v1.2.0 |
| Local path | /Users/me/projects/my-module |
Pass a source on the command line with --custom-source; separate several sources with commas.
npx bmad-method install --directory . --custom-source /path/to/my-module --tools claude-code --yes
A source with .claude-plugin/marketplace.json lists its plugins for you to pick from. Without one, the installer scans the folder for skills and treats them as one module. Quick update (--action quick-update) refreshes installed modules from their recorded sources, and a full update (--action update) lets you add or remove them.