bglad

bglad is extra skills on top of BMad. It does not change BMad’s own documentation.

You pick one path and run it from the help menu:

• Solo (SO) — one person, one chat, the whole path
• Team (TE) — product owner starts, then Design, implement, required review, required tests

Specs live in one place, chosen at install: Jira, Confluence, or local markdown. When the work is ready to land, open a GitLab merge request or a GitHub pull request — whichever your overlay names — then a short note in knowledge/.

What to do

1. Install in your product repo
2. Run SO or TE (or the next step if you are already mid-path)
3. Words and menu codes if SO / TE / MR are new

That is the whole overlay. Config and squads come later, when you need hosts or per-folder defaults.

Paths

• Solo — one developer, whole path
• Team — named roles; review and tests are required even if the same person wears those hats

Ship

• File a ticket
• Open a merge request or pull request
• Clone onto supported releases
• Knowledge note

Configure

When you need hosts, reviewers, or per-folder defaults:

• Config layers
• Squad picker
• Override defaults

BMad Method docs stay at docs.bmad-method.org. See How we sit on BMad.