What problem does it solve? Setting up a BMad module in a project requires writing configuration to multiple files, migrating legacy per-module configs, and registering help entries — doing this by hand is error-prone and leaves stale values behind. ## Core Features & Use Cases - Config Merging: Collects user preferences and writes them to _bmad/config.yaml (shared settings) and _bmad/config.user.yaml (personal settings like user_name and communication_language) using an anti-zombie pattern that removes stale entries before writing. - Legacy Migration: Detects old per-module config files, uses their values as fallback defaults, and deletes them after a successful merge. - Help Registration & Cleanup: Merges module capabilities into module-help.csv and removes legacy installer directories after verifying skills are installed at .claude/skills/. - Use Case: A user says "install the bmb module" — the skill reads module.yaml, prompts for preferences, writes both config files, registers help entries, and cleans up legacy directories in one guided flow. ## Quick Start Ask the assistant to install and configure the module in this project, optionally providing values inline such as your name and preferred language to skip interactive prompts.