bmad-bmb-setup

Set up and migrate BMad Builder module configuration into shared _bmad files.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-bmb-setup-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-bmb-setup
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-bmb-setup-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the manual friction of installing and reconfiguring the BMad Builder module in a project, especially when you need to consolidate legacy setup files into the current shared configuration format.

Core Features & Use Cases

  • Module installation: Collects project and user preferences, then writes the shared BMad config files in the correct locations.
  • Legacy migration: Detects older per-module installer files, uses them as fallback defaults, and cleans them up after a successful merge.
  • Project onboarding: Helps teams bootstrap BMad Builder with consistent output paths, help entries, and module metadata.
  • Use case: A developer upgrades an existing project from an older BMad layout and wants one clean, current setup without losing prior configuration values.

Quick Start

Ask the assistant to set up the BMad Builder module in your project, collect your preferences, and write the shared _bmad configuration while migrating any legacy files.

Frequently Asked Questions about bmad-bmb-setup

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

FAQPage Schema
How do I migrate legacy per-module BMad configuration files into shared _bmad files?

To migrate legacy BMad configuration, the setup detects older per-module installer files, uses them as fallback defaults, and safely merges them into shared _bmad files before cleaning up the legacy configs.

What is the best way to set up BMad Builder module configuration in an existing project?

The best way to set up BMad Builder is to use an automated module installer that collects project preferences and writes the shared YAML metadata and configuration files in the correct locations.

Does the BMad Builder setup require YAML module metadata to run?

Yes, YAML module metadata is required to set up the BMad Builder module, as it drives the configuration generation and ensures the anti-zombie merges execute correctly during the file consolidation.

Can I consolidate legacy BMad installer files without losing my previous configuration values?

Yes, you can consolidate legacy BMad installer files safely because the migration process uses older per-module configurations as fallback defaults, ensuring no previous values are lost during the cleanup.

Why does my BMad Builder project onboarding need an anti-zombie merge?

An anti-zombie merge is needed during BMad Builder onboarding to prevent orphaned or duplicate configuration entries from persisting when consolidating legacy per-module files into the shared _bmad configuration.

Are there limitations when updating shared _bmad configuration files from older BMad layouts?

A key limitation when updating shared _bmad files is that the migration requires valid YAML module metadata and depends on the pyyaml library to correctly parse and execute the configuration consolidation.