bmad-customize

To customize agent behavior without modifying core code, translate your intent into per-skill TOML overrides. These overrides adjust agents and workflows by placing configuration files under {project-root}/_bmad/custom, leaving base skills untouched.

The best way to structure TOML overrides is to create a customize.toml file requiring an [agent] or [workflow] block. This file routes and authors team and user overrides under the {project-root}/_bmad/custom directory for both agent and workflow surfaces.

Yes, you can manage overrides across both project-local and user-global setups. The system discovers, routes, and verifies TOML overrides for both surfaces, storing team and user configurations under {project-root}/_bmad/custom.

The resolver merges configuration changes by layering per-skill TOML overrides over base configurations. It validates the merged outcomes before deployment to ensure the adjusted agent or workflow behavior operates correctly without altering core skill code.

You need an [agent] or [workflow] block in customize.toml whenever translating user intent into per-skill overrides. This required block dictates whether the TOML configuration adjusts agent behavior or modifies workflow surfaces.

A key limitation is that overrides require a valid [agent] or [workflow] block in customize.toml to function. Additionally, configurations must be stored under {project-root}/_bmad/custom and validated by the built-in resolver before deployment to prevent merge conflicts.