bmad-bmb-setup

Install and configure a BMad module with config files and metadata.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-bmb-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/.trae/skills/bmad-bmb-setup
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-bmb-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Installs and configures a BMad module into a project, unifying module identity and preferences into a centralized setup flow.

Core Features & Use Cases

  • Collects user preferences and writes them to three config files: a root _bmad/config.yaml, a per-user _bmad/config.user.yaml, and a module-capabilities CSV for the help system.
  • Migrates legacy per-module and core configurations, consolidating values and performing cleanup after setup.
  • Creates required output directories and derives module metadata from assets/module.yaml to enable IDE synchronization and consistent deployment.

Quick Start

Run the module setup 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 configure a BMad module in my project?

Legacy configuration migration consolidates old per-module and core configuration values into the new centralized setup files. It performs this consolidation automatically and executes cleanup after the setup process completes.

How does the BMad builder setup handle per-user settings?

Per-module variable user_settings are stored in a dedicated _bmad/config.user.yaml file, while the rest of the configuration resides in the standard config.yaml. This separation ensures user-specific preferences do not overwrite core module configurations.

Do I need PyYAML to run the module setup workflow?

Yes, PyYAML is a required dependency to run the module setup workflow. The setup process needs it to parse the assets/module.yaml file, derive module metadata, and write the generated YAML configuration files to the project root.

What is the anti-zombie merge pattern in module configuration?

The anti-zombie merge pattern is enforced during configuration migration to prevent stale or conflicting legacy values from persisting. It ensures that old per-module and core configurations are cleanly consolidated and safely cleaned up after the setup completes.

How do I generate module metadata from a YAML file for IDE synchronization?

The setup workflow derives module metadata directly from assets/module.yaml to enable IDE synchronization and consistent deployment. It processes this YAML source file alongside creating output directories to complete the end-to-end configuration process.