Install BGlad

Install BGlad in the product directory: the folder that should contain _bmad/. In a git monorepo that is the product folder (for example client/), not the git root. Requires Node.js 20.12+, npx, and uv (Python 3.11+). Pin is BMad 6.12.0.

You do not check BGlad out next to the product. From the product repo, npx downloads the public bglad-method package and runs the installer. No GitLab membership is required.

BMad copies skills. It does not run a custom-module post-install hook. The installer is the bglad-method binary in this repo. Run the command from the product repo — install refuses to target this workshop.

Fresh product repo

From the product repo (MIT):

npx bglad-method install

Pin a release with @: npx bglad-method@0.1.0 install.

A fork you can clone uses that fork’s git URL the same way:

npx --yes git+https://gitlab.com/zarko.susnjar/bglad.git install

Pass --directory /path/to/product if your current directory is not the product repo.

Useful flags: --yes, --tools, --list-tools, --spec-store, --list-spec-stores, --jira-project, --git-forge, --team-field, --jira-account, --gitlab-username, --github-username, --overlays-only.

update --directory /path/to/product re-applies shipped bglad skills and bglad-how-we-work.md, writes _bmad/_config/bglad-install.json, and leaves _bmad/custom/*.toml and how-we-work.local.md alone.

That command runs npx bmad-method@6.12.0 install with --custom-source pointing at the fetched BGlad tree and the AI setups you picked, then adds Remy (delivery agent), Dev, Analysis, and required review/QA menus, how-we-work, help rows, and an org overlay for tickets and git hosting. Setup questions use BMad’s installer prompts: AI setups, spec location, a typed Jira project key, and GitLab or GitHub. It checks glab or gh, and a Jira MCP or jira CLI, and does not ask for a username or Jira account when those are present. It does not rewrite BMad’s own help rows or replace Build / test-generation / PRD workflow files.

After install

1. Open the help menu. You should see DEV, AN, RV, and QA.
2. Developers run Dev. Product owners run Analysis to prepare incoming stories. Overlay work uses DEV, not stock BD, and AN, not stock PRD.
3. Fill _bmad/custom/bglad-ticket-mr.toml if hosts are still empty: Jira (if you use it) and GitLab or GitHub (git_forge). The installer infers github.com / gitlab.com from origin when it can. Anything else it asks — it does not assume a host.

AI setups (where skills land)

BMad already copies skills per --tools. BGlad asks first (you can pick more than one), then passes that list through. .agents is a folder, not a product — Cursor, GitHub Copilot, and Codex all use .agents/skills.

You type	BMad id	Skills land in
claude	claude-code	.claude/skills
cursor	cursor	.agents/skills
copilot	github-copilot	.agents/skills
codex	codex	.agents/skills

--yes without --tools uses Claude (claude-code).

npx bglad-method install --tools claude,cursor

npx bglad-method install --list-tools

Spec location

Dev and Analysis keep one spec. The installer asks where it lives. --yes without --spec-store uses Jira.

You type	Where the spec lives	Connector
jira	Jira Task description (Problem, Acceptance, Design, Test notes, Open questions)	Jira MCP or jira CLI. Overlay work HALT if missing
confluence	Confluence page with the same headings. Pass --confluence-host and --confluence-space	Confluence MCP or Confluence CLI/REST. Overlay work HALT if missing
markdown	Local files under _bmad-output (BMad’s document folder, not stock bmad-prd)	None

npx bglad-method install --spec-store confluence --confluence-space ENG

npx bglad-method install --list-spec-stores

The choice is written into _bmad/custom/bglad-ticket-mr.toml (spec_store) and the Spec location section of bglad-how-we-work.md. Filing a Jira ticket for tracking (bglad-ticket-mr) is separate from where the spec lives.

Check an overlay

Validate-only reads _bmad/custom/bglad-ticket-mr.toml and prints problems. It does not change the file. From a product repo, with BGlad checked out:

uv run /path/to/bglad/.agents/skills/bglad-setup/scripts/install.py validate --directory .

It flags a jira_host that is not a base URL, a team with an empty jira_component or jira_development_team, and a configured doc path that is not in the repo.

Existing BMad install

From the product repo:

npx bglad-method install --overlays-only

Local clone (optional)

Only if you already have BGlad checked out — for example while changing the installer. From the product repo, point npx at that folder:

npx --yes ../bglad install

Verify

bmad-help lists the overlay menus. Full names are on Words and menu codes:

• DEV Dev (developers), AN Analysis (incoming stories)
• DS optional Design, RV required review, QA required tests
• MR tickets and a GitLab merge request or GitHub pull request, NOTE distilled knowledge

Also check _bmad/custom/bglad-how-we-work.md exists, and stock BMad PRD/Build are still there unpatched. A squad overlaying defaults: Override defaults.