What problem does it solve? Setting up a BMad module requires writing configuration values to multiple files, migrating legacy per-module configs, registering help entries, and cleaning up installer directories. Doing this manually is error-prone and leaves stale config values behind. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into shared config.yaml and config.user.yaml files using an anti-zombie pattern that removes stale entries before writing fresh ones. - 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 help entries into module-help.csv and removes legacy installer directories after verifying skills are installed at .claude/skills/. - Use Case: When a user asks to install or configure a BMad module, this skill collects preferences, writes the three config files, creates output directories, and cleans up legacy installer packages in one guided flow. ## Quick Start Ask the agent to install and configure the BMad module for your project, providing any preferences such as your name and preferred language. ## Quick Start Install the BMad module in my project and configure it with my user name and preferred language.