bmad-customize

Invoke the customize flow and describe the change in plain English. The Skill reads the target's customize.toml, composes a sparse TOML override, and writes it to _bmad/custom/ as a team or user file after your confirmation.

Team overrides use the {skill-name}.toml filename, are committed to the repository, and suit policies and org conventions. User overrides use {skill-name}.user.toml, are gitignored, and suit personal tone, private facts, and shortcuts.

No. Overrides only cover fields exposed in the target's customize.toml, such as templates, scalars, and append arrays. For step logic changes, the Skill suggests activation_steps_prepend/append as approximations or building a custom skill with bmad-builder.

Scalars like icon and role are replaced by the override. Arrays like persistent_facts and principles append in order. Keyed arrays of tables merge by their code or id key, with matching keys replaced and new keys appended.

The Skill falls back to a manual merge: it reads the base customize.toml plus any team and user override files, applies base then team then user ordering with the standard merge rules, and describes how the changed fields resolve.

Common causes are a wrong field name, wrong merge mode (scalar versus array), or wrong scope. The Skill re-enters the composition step using the resolver output as context to diagnose and correct the override.