bmad-bmb-setup

Installs and configures the BMad Builder module into a project's shared config files.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-bmb-setup-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-bmb-setup
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-bmb-setup-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and assets (resource) components.

What problem does it solve? Setting up a BMad module requires writing consistent YAML configuration across multiple files, migrating legacy per-module configs, and registering help entries — a manual process prone to stale values and missed cleanup steps. ## Core Features & Use Cases - Config Merging: Writes core and module settings to _bmad/config.yaml and personal settings to _bmad/config.user.yaml using an anti-zombie pattern that removes stale entries before writing fresh ones. - Legacy Migration: Detects old per-module config files, uses their values as fallback defaults, and deletes them after a successful merge. - Help Registration & Cleanup: Merges module capabilities into module-help.csv and removes legacy installer directories after verifying skills are installed at .claude/skills/. - Use Case: After installing the BMad Builder module, run this skill to collect your preferences (user name, language, output folders), consolidate any existing installer config, and produce a clean _bmad/ directory containing only config files. ## Quick Start Ask the assistant to install and configure the BMad Builder module in this project, optionally providing values like your name and preferred language inline.

Frequently Asked Questions about bmad-bmb-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the BMad Builder module in a project?

Run the bmad-bmb-setup skill, which reads module.yaml for variable definitions, prompts for your preferences, and writes them to _bmad/config.yaml and config.user.yaml. You can also pass values inline to skip interactive prompting.

How do I migrate legacy BMad per-module config files?

The setup detects legacy configs at _bmad/bmb/config.yaml and _bmad/core/config.yaml automatically. Matching values become fallback defaults, and the legacy files are deleted after a successful merge into the new shared config format.

What is the difference between config.yaml and config.user.yaml in BMad?

config.yaml holds shared project settings like output_folder and module values, while config.user.yaml stores personal settings like user_name and communication_language that are intended to be gitignored. User-only keys are never written to the shared config.

Why does the BMad setup script reject the {project-root} token?

The {project-root} token is only valid inside config values, not filesystem path arguments. The scripts exit with an error if it appears in --config-path, --target, or similar arguments, so you must resolve it to the actual project root before running.

Is it safe to remove legacy BMad installer directories?

Yes, the cleanup script first verifies that every skill in the legacy directories exists at .claude/skills/ before removing anything. Missing directories from prior runs are not errors, making the operation idempotent.