bmad-bmb-setup

Installs and configures the BMad Builder module by writing shared YAML config files.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-bmb-setup-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-bmb-setup
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-bmb-setup-watchthelight

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 collecting user preferences, merging them into shared config files, migrating legacy per-module configs, and cleaning up installer directories — a multi-step process that is error-prone when done manually. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into _bmad/config.yaml and personal settings into _bmad/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 deletes them after a successful merge. - Safe Cleanup: Verifies every skill exists at .claude/skills/ before removing legacy installer directories, and rejects unresolved {project-root} path tokens. - Use Case: After installing the BMad Builder module, run this skill to answer a few prompts (user name, language, output folders) and have all config files, help CSV entries, and directory cleanup handled automatically. ## Quick Start Ask the assistant to install and configure the BMad Builder module, optionally providing values like your name and preferred language inline to skip interactive prompts.

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 configuration values, and writes them to _bmad/config.yaml and _bmad/config.user.yaml. You can pass values inline to skip interactive prompting.

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

The setup skill automatically detects legacy configs at _bmad/bmb/config.yaml and _bmad/core/config.yaml, uses matching values as fallback defaults, and deletes the legacy files 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-specific values, while config.user.yaml stores personal settings like user_name and communication_language that are intended to be gitignored and never shared.

Why does the BMad setup script fail with an unresolved token error?

The scripts reject any path argument still containing the literal {project-root} token. You must resolve it to the actual project root path before running, since the token is only valid inside config values, not filesystem paths.

Is it safe to delete legacy BMad installer directories?

Yes, the cleanup script verifies that every skill found in legacy directories already exists at .claude/skills/ before removing anything. Missing directories from prior runs are treated as success, making the operation idempotent.