What problem does it solve? Setting up a BMad module requires collecting user preferences, merging them into shared configuration 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 - Guided configuration collection: Prompts for core settings (user name, languages, output folder) and module variables defined in assets/module.yaml, with support for headless/argument-driven installs. - Config merging with anti-zombie pattern: Writes core values to _bmad/config.yaml, user-only settings to config.user.yaml, and module help entries to module-help.csv, removing stale entries before writing fresh ones. - Legacy migration and cleanup: Reads old per-module config files as fallback defaults, deletes them after merging, and removes legacy installer directories only after verifying skills exist at the installed location. - Use Case: A developer adds the BMad Builder module to a project and runs the setup to consolidate old installer configs into the new shared config format, then cleans up leftover package directories. ## Quick Start Ask the assistant to install and configure the BMad Builder module in this project, optionally providing values like your user name and preferred language.