{setup-skill-name}

To automate module setup, provide a module.yaml and user answers JSON to the setup process. It merges core and module settings into _bmad/config.yaml using an anti-zombie strategy that cleanly replaces existing module sections for repeatable deployments.

The anti-zombie strategy is a configuration merge mechanism that overwrites existing module sections in _bmad/config.yaml. It prevents obsolete or orphaned settings from persisting when a new module is installed or an existing one is reconfigured.

To migrate legacy settings, the setup reads legacy directory values as fallbacks and automatically cleans up old configuration files. This ensures smooth transitions when applying new module.yaml configurations to a project.

Yes, you can maintain per-user preferences in _bmad/config.user.yaml. This separates sensitive or individual values from the shared _bmad/config.yaml, keeping team deployments scalable without exposing personal configurations.

You need to provide the module.yaml file containing module metadata and an answers JSON object with your specific configurations. The setup consumes these inputs to install and configure the BMad module into your project.

Old configuration files may conflict with new module settings due to legacy formats. The setup process addresses this by consuming legacy directory values as fallbacks and performing a cleanup of old config files during the migration.