bmad-bmb-setup

BMad Builder configuration setup merges module settings from assets/module.yaml into shared configuration files while applying anti-zombie config merging and user setting segregation to prevent conflicts during the setup process.

Migrating legacy BMad configuration involves detecting older per-module config locations, using them as fallback defaults, and cleaning them up after successfully merging into shared consolidated config files.

Yes, the setup process requires YAML-based module definitions, specifically reading from assets/module.yaml to merge core and module settings into shared configuration files.

Anti-zombie config merging consolidates core and module settings into shared files while explicitly segregating user settings, preventing overwritten custom configurations during BMad setup.

Yes, the update workflow merges new module settings from YAML definitions into shared config files while user setting segregation ensures custom configurations are preserved and not overwritten.

Migration requires valid YAML-based module definitions to proceed; if older per-module config locations are missing, the setup cannot use fallback defaults for the consolidated merge.