What problem does it solve? Setting up a BMad module requires writing shared config files, separating user-specific settings, registering help entries, and cleaning up legacy installer directories — a multi-step process that is error-prone when done manually. ## Core Features & Use Cases - Config Merging: Writes core settings to _bmad/config.yaml and personal settings (user_name, communication_language) to a gitignored config.user.yaml, using an anti-zombie pattern that removes stale module 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. - Safe Cleanup: Verifies every legacy skill exists at .claude/skills/ before removing installer package directories, with idempotent behavior for repeated runs. - Use Case: After installing the BMad Builder module, run this skill to consolidate scattered installer configs into the shared _bmad/config.yaml format and clean up over 100 leftover package files. ## Quick Start Ask the agent to install and configure the BMad Builder module, optionally providing values inline such as your name and preferred language.