bmad-bmb-setup

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

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-bmb-setup-5onyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/5onyy/essential-ai-agent-skills/tree/main/.cursor/skills/bmad-bmb-setup
Command: npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-bmb-setup-5onyy

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 shared config files, separating user-specific settings, registering help entries, and cleaning up legacy installer directories — a multi-step process that is error-prone when done manually. ## Core Features & Use Cases - Config Merging: Writes core settings to _bmad/config.yaml and personal settings (user_name, communication_language) to a gitignored config.user.yaml, using an anti-zombie pattern that removes stale module 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. - Safe Cleanup: Verifies every legacy skill exists at .claude/skills/ before removing installer package directories, with idempotent behavior for repeated runs. - Use Case: After installing the BMad Builder module, run this skill to consolidate scattered installer configs into the shared _bmad/config.yaml format and clean up over 100 leftover package files. ## Quick Start Ask the agent to install and configure the BMad Builder module, optionally providing values inline such as your name and preferred language.

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 and configure the BMad Builder module?▼

Run the setup skill, which reads module.yaml for variable definitions, prompts for values like output folders and language, then writes them to _bmad/config.yaml and config.user.yaml. You can also pass values inline to skip interactive prompting.

How does BMad config migration from legacy per-module files work?▼

The merge-config.py script reads old config.yaml files from _bmad/bmb/ and _bmad/core/, uses matching values as fallback defaults, and deletes the legacy files after a successful merge. Only keys matching the current schema are carried forward.

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

config.yaml holds shared project settings like output_folder and module variables, while config.user.yaml stores personal settings like user_name and communication_language and is intended to be gitignored. Module variables marked user_setting: true also go exclusively to config.user.yaml.

Is it safe to delete legacy BMad installer directories?▼

Yes, the cleanup-legacy.py script verifies that every skill in the legacy directories exists at .claude/skills/ before removing anything. The script is idempotent, so already-cleaned directories are skipped without errors.

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

It is a literal token stored in config files that signals values are relative to the project root, never substituted with an actual path. Only filesystem operations like creating output directories resolve it to the real path.