Install bglad
Install bglad at the product monorepo root. Requires Node.js 20.12+, npx, and uv (Python 3.11+). Pin is BMad 6.12.0.
BMad copies skills. It does not run a custom-module post-install hook. bglad-method is the installer, same shape as npx bmad-method install.
Fresh product repo
Section titled “Fresh product repo”From a clone of bglad:
npx --yes /path/to/bglad installYou can pass a git URL of that clone instead of a path. Useful flags: --yes,
--tools, --list-tools, --spec-store, --list-spec-stores,
--jira-project, --jira-account, --gitlab-username, --github-username,
--overlays-only.
That command runs npx bmad-method@6.12.0 install with --custom-source bglad
and the AI setups you picked, then adds bglad’s extras: Remy (delivery agent),
Solo and Team menus, how-we-work, help rows, an org overlay for tickets and
git hosting, gitignored identity. It does not rewrite BMad’s own help rows
or replace Build / test-generation / PRD workflow files.
The installer refuses to install into this workshop repo.
After install
Section titled “After install”- Open the help menu. You should see SO and TE.
- Pick Solo or Team.
- Fill
_bmad/custom/bglad-ticket-mr.tomlif hosts are still empty: Jira (if you use it) and GitLab or GitHub (git_forge). The installer infersgithub.com/gitlab.comfromoriginwhen it can. Anything else it asks — it does not assume a host.
AI setups (where skills land)
Section titled “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 --yes /path/to/bglad install --tools claude,cursornpx bglad-method install --list-tools prints the same table.
Spec location
Section titled “Spec location”Solo and Team 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) | Jira MCP or jira CLI. Solo/Team HALT if missing |
confluence | Confluence page with the same headings. Pass --confluence-host and --confluence-space | Confluence MCP or Confluence CLI/REST. Solo/Team HALT if missing |
markdown | Local files under _bmad-output (BMad’s document folder, not stock bmad-prd) | None |
npx --yes /path/to/bglad install --spec-store confluence --confluence-space ENGnpx bglad-method install --list-spec-stores prints the list. 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.
Existing BMad install
Section titled “Existing BMad install”npx --yes /path/to/bglad install --overlays-onlyVerify
Section titled “Verify”bmad-help lists the overlay menus. Full names are on Words and menu codes:
- SO Solo, TE Team start
- Team steps: DS Design, DEV implement, RV review, QA tests
- MR tickets and a GitLab merge request or GitHub pull request, NOTE knowledge note
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.