Override defaults

A squad in a monorepo (for example tooling client/ and server/) can overlay bglad. The Solo and Team paths stay the same. You change defaults, not the skills themselves.

BMad already merges three TOML layers per skill. bglad skills use that same resolver. Merge rules and sparse-file advice live on How to Customize BMad. Do not copy a full customize.toml into an override.

What to overlay (bglad side)

Pick the smallest surface that matches the change.

You want to change	Put it here
Jira component, reviewers, commit/MR/PR title for one folder	[workflow.teams.<id>] in _bmad/custom/bglad-ticket-mr.toml — squad picker
Test commands, knowledge folder, “do not edit generated files”	_bmad/custom/bglad-how-we-work.local.md (setup never overwrites this)
Extra facts or startup steps for a bglad skill	Sparse _bmad/custom/bglad-<skill>.toml (committed) or bglad-<skill>.user.toml (gitignored)
Your Jira account / GitLab or GitHub username	_bmad/custom/bglad-ticket-mr.user.toml

Example: two trees, one squad, same Jira project, different component. GitLab:

# _bmad/custom/bglad-ticket-mr.toml  (only the squad table you add)

[workflow]
git_forge = "gitlab"

[workflow.teams.tooling]
name = "Tooling"
path_prefixes = ["client/", "server/"]
jira_component = "Tooling"
gitlab_mr_reviewers = ["alice"]

Same shape on GitHub: git_forge = "github" and github_pr_reviewers.

Example: extra context for implement, without replacing the required review ASK.

_bmad/custom/bglad-dev.toml

[workflow]
persistent_facts = [
  "file:{project-root}/client/CONTRIBUTING.md",
]
activation_steps_append = [
  "If cwd is under server/, honor server/README.md run instructions.",
]

persistent_facts and activation_steps_* append. on_complete is a scalar — a team overlay replaces the whole string. Do not override on_complete unless you keep the same next step (review after DEV, QA after review, MR after QA).

Skill overlay file names match the folder: bglad-solo, bglad-team, bglad-architecture, bglad-dev, bglad-review, bglad-qa, bglad-ticket-mr, bglad-knowledge, bglad-agent-delivery.

See every field a skill accepts in its shipped .agents/skills/<name>/customize.toml. Edit the overlay, not that file.

What reinstall rewrites

npx bglad-method install (and --overlays-only) rewrites these so overlay menus stay correct:

• _bmad/custom/bmad-agent-dev.toml (Amelia: SO, DEV, RV, QA, MR, NOTE)
• _bmad/custom/bmad-agent-pm.toml (John: TE, MR)
• _bmad/custom/bmad-agent-architect.toml (Winston: DS)
• _bmad/custom/bglad-how-we-work.md
• bglad rows in _bmad/_config/bmad-help.csv

Do not put squad rules in those agent files. They will not survive the next install. Extra Amelia menu items belong in bmad-agent-dev.user.toml (personal) or wait for a later merge-preserving install.

Install does not overwrite _bmad/custom/bglad-ticket-mr.toml once it exists, does not touch bglad-*.toml skill overlays, and never writes bglad-how-we-work.local.md.

Do not

• Edit .agents/skills/bglad-*/customize.toml or SKILL.md in the product repo (the next bglad copy replaces them).
• Overlay stock bmad-prd, bmad-build, bmad-architecture, or BMad QA workflow TOMLs. Setup deletes those if it finds them. Overlay work is Solo or Team.
• Patch BMad help rows or replace BD / SO / TE with each other.
• Skip required review or tests by blanking on_complete.

Config layers is the merge diagram. Squad picker is how a folder becomes a team. Everything else about TOML shape (scalars, arrays, [[agent.menu]] by code) is BMad customize.