{setup-skill-name}

Automating BMad module setup involves reading metadata from assets/module.yaml, collecting user preferences, and writing configurations to _bmad/config.yaml and _bmad/config.user.yaml. It also registers module capabilities in module-help.csv to ensure consistent project structure.

The best way to migrate legacy BMad configurations is to apply legacy defaults during module setup while cleaning up existing module sections. This anti-zombie migration prevents zombie data by removing old configs from _bmad/config.yaml and config.user.yaml.

Yes, BMad module setup requires the pyyaml dependency to parse and write YAML files. It uses pyyaml to read module metadata and update the core and module sections within _bmad/config.yaml and _bmad/config.user.yaml.

BMad module configuration handles per-module settings by writing user preferences to _bmad/config.user.yaml. It registers help system capabilities by updating entries in _bmad/module-help.csv, ensuring modules are properly documented and accessible.

Yes, you can use BMad setup to install a Godot module into an existing project. The setup process reads module metadata, collects your preferences, and updates the necessary _bmad configuration files to integrate the module seamlessly.

Outdated configuration data persists when legacy values are not properly migrated. The BMad setup performs anti-zombie migrations by cleaning up existing module sections in _bmad/config.yaml and applying legacy defaults to prevent stale zombie data.