What problem does it solve? Setting up a BMad module in a project requires collecting user preferences, writing them consistently across shared and personal config files, registering help entries, and cleaning up legacy installer files. Doing this manually is error-prone and leaves stale configuration behind. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into _bmad/config.yaml and personal settings into _bmad/config.user.yaml 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, the skill collects preferences (with support for headless arguments), writes all config files via scripts, creates output directories, and confirms the result. ## Quick Start Ask the assistant to install and configure the module in your project, optionally providing values like your user name and preferred language inline.