BGlad

BGlad is an additional layer on the BMad Method.

Dev (DEV) is the default for developers: same entry as stock Build, then three org gates (Problem and Acceptance before code, required review, required write-and-run tests).

Analysis (AN) is product-owner analysis of an incoming story. Convert a third-party story into DEV-ready Jira tasks, then stop. Design (DS) is optional the same way.

The spec (Jira, Confluence, or local markdown — chosen at install) is where everything we know about the work is distilled. Unanswered reporter questions sit under Open questions on that same spec. Later development starts from that spec, the way it would from architectural decision records.

When the work is ready to land, open a GitLab merge request or a GitHub pull request — whichever your overlay names. Then write those decisions into knowledge/ so the next piece of work can start from them.

What to do

1. Install in your product repo
2. Developers run DEV (then required RV and QA). Product owners run AN to prepare incoming stories
3. Words and menu codes if DEV / AN / MR are new

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

Paths

• Dev — developers. Build-shaped entry plus gates
• Analysis — product owners. Incoming story to DEV-ready tasks; review and tests stay required after implement

Ship

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

Configure

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

• Config layers
• Squad picker
• Override defaults

How BGlad sits on the Method: How we sit on BMad. Method docs: docs.bmad-method.org.