bmad-bmb-setup

Automate module setup and config migration by reading module metadata from assets/module.yaml and consolidating values into _bmad/config.yaml and _bmad/config.user.yaml. The process loads old per-module configs as defaults, applies them during setup, and cleans up legacy files automatically.

The best way to clean up legacy per-module configurations is using an anti-zombie update pattern that removes existing module sections before writing. This ensures a consistent configuration state by loading old configs as defaults, then safely deleting legacy files.

Yes, you can generate shared config and per-user settings files automatically. The setup consolidates core and module values into _bmad/config.yaml for shared configuration and _bmad/config.user.yaml for per-user settings, creating required directories under the project root.

Yes, the BMad Builder setup requires pyyaml to parse and wire up module config files. It reads module metadata from assets/module.yaml and processes the data into centralized configuration files, relying on pyyaml for YAML parsing and consolidation.

Module config setup leaves duplicate or zombie entries when existing module sections are not removed before writing. An anti-zombie update pattern prevents this by deleting old sections prior to writing new consolidated values into _bmad/config.yaml.

Register module capabilities for a help system during setup by running the automated installation process. It creates required directories under the project root, registers the module capabilities, and ensures the configuration state is consistent across projects.