bmad-customize

To customize BMad agent behavior, you write sparse TOML override files in your project's _bmad/custom directory. This approach modifies persona, templates, and workflow settings without copying or altering the original base configurations.

BMad workflow overrides must be placed as TOML files under the project's _bmad/custom directory. The Skill automatically routes your configuration requests to the correct team or user override file within this specific folder structure.

Applying TOML configuration overrides requires reading the target skill's customize.toml file first. The Skill then translates your plain-language persona requests into the correct sparse TOML overrides and writes them to the appropriate project folder.

Yes, you can verify existing BMad customization overrides. The Skill checks current override files, summarizes what has already been changed, and validates the merged configuration results after your edits are applied to ensure correctness.

Yes, bmad-customize supports both team-level and user-level configuration scopes. It routes product lead requests for global workflow changes to team override files, while directing personal agent shortcuts to individual user override files automatically.

You should use sparse TOML overrides when you need to change specific persona behaviors or templates across projects. This method prevents copying full base configs, ensuring your customizations remain isolated, verifiable, and maintainable within the _bmad/custom directory.