bmad-bmb-setup

Installs and configures the BMad Builder module by merging YAML config files and help CSV entries.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-bmb-setup-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-bmb-setup
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-bmb-setup-wizarck

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 manually writing configuration files, registering help entries, and migrating legacy per-module configs, which is error-prone and leaves stale values behind. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into _bmad/config.yaml and user-only settings into config.user.yaml using an anti-zombie pattern that removes stale entries. - Legacy Migration: Detects old per-module config files, uses their values as fallback defaults, and cleans up legacy directories after verifying skills are installed. - Help Registration: Merges module capability entries into a shared module-help.csv for the help system. - Use Case: A user says "install bmb module" and the Skill collects preferences, writes both config files, registers help entries, creates output directories, and removes installer leftovers. ## Quick Start Ask the assistant to install and configure the BMad Builder module in your project.

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?▼

Invoke the setup skill and answer the configuration prompts, or pass arguments like "accept all defaults" for headless setup. The skill writes config.yaml, config.user.yaml, and module-help.csv under the _bmad directory.

How does BMad module config migration from legacy format work?▼

The merge scripts read old per-module config.yaml files from _bmad/bmb/ and _bmad/core/, use matching values as fallback defaults, then delete the legacy files. The cleanup-legacy.py script removes leftover directories after verifying skills exist at .claude/skills/.

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 meant to be gitignored. Module variables marked user_setting: true also go to config.user.yaml.

What does the {project-root} token mean in BMad config values?▼

It is a literal placeholder stored in config files indicating the path is relative to the project root, not the skill root. It is only resolved to an actual path when creating directories on disk.

Why does BMad setup fail when cleaning up legacy directories?▼

Cleanup fails if a skill found in legacy directories is missing from the installed .claude/skills/ location, since the script verifies every skill before removal. Reinstall the missing skills, then rerun the cleanup step.