How we sit on BMad
BGlad is an additional layer on the BMad Method. Method docs stay the source for Method (product requirements, architecture, Build, Quick Dev, the help catalog). BGlad does not fork those pages or patch BMad’s own help rows.
What BGlad adds:
- Dev — developers. Same entry as stock Build, plus Problem and Acceptance before code, required review, required write-and-run tests
- Analysis — product-owner analysis of incoming stories; Design (DS) is optional the same way
- One spec (
ticket-spec.md), location chosen at install: Jira, Confluence, or local markdown. That spec is the distilled picture later work starts from. Unanswered reporter items sit under Open questions - GitLab merge requests or GitHub pull requests via the ticket skill (
bglad-ticket-mr), fromgit_forge - Distilled decisions in
knowledge/after the change request (architectural decision records)
Stock bmad-prd, bmad-build, and BMad’s test-generation skill remain
installed. BMad’s developer agent (Amelia) still has a Build menu (BD).
Overlay work uses Dev (or Analysis when a product owner prepares incoming
stories) instead of those BMad skills. That is true whether the spec lives on
Jira, Confluence, or markdown.
Same spec headings everywhere: Problem, Acceptance, Design, Test notes, Open questions.
A product team overlays defaults with BMad’s three-layer TOML merge plus BGlad squad tables — Override defaults.
Words and menu codes lists every help-menu code.