Skip to content
bglad

How we sit on BMad

BMad documentation stays 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:

  • Solo and Team — overlay paths, documented here
  • One spec (ticket-spec.md), location chosen at install: Jira, Confluence, or local markdown
  • GitLab merge requests or GitHub pull requests via the ticket skill (bglad-ticket-mr), from git_forge
  • A knowledge/ note after the change request

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 Solo or Team 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.

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.