Words and menu codes
Help-menu codes are the same words as the step, shortened:
| Menu | Say this | Skill |
|---|---|---|
| DEV | Dev / implement | bglad-dev |
| AN | Analysis | bglad-analysis |
| DS | Design | bglad-architecture |
| RV | Review | bglad-review |
| QA | Tests / QA | bglad-qa |
| MR | Ticket, merge request, or pull request | bglad-ticket-mr |
| NOTE | Knowledge | bglad-knowledge |
| REMY | Remy (delivery) | bglad-agent-delivery |
MR files a Jira issue, clones a released bug, or opens the change request
on your git host: a GitLab merge request or a GitHub pull request,
from git_forge on the org overlay. Empty git_forge → the skill asks.
Dev is the default for developers (Build-shaped entry plus gates). Analysis is how product owners prepare incoming stories. Needing reporter answers is Open questions on the spec, not a skill switch. Overlay work uses DEV, not stock Build (BD), and AN, not stock PRD.
Other words you will see
Section titled “Other words you will see”| Word | Meaning |
|---|---|
| Overlay | Additional layer on the BMad Method. Method itself stays as shipped |
| Override | Sparse _bmad/custom/ TOML (or a squad table) that changes defaults. See Override defaults |
| Spec location | Where overlay work keeps Problem / Acceptance / Design / Test notes / Open questions: Jira, Confluence, or local markdown (_bmad-output). Chosen at install (spec_store) |
| Jira Task | One of those locations. Needs Jira MCP or jira CLI |
| Confluence spec | Same headings on a wiki page. Needs Confluence MCP or CLI |
| Git forge | gitlab or github on the org overlay. No built-in default |
| Merge request | GitLab change request |
| Pull request | GitHub change request |
| Product owner | Analysis: convert a third-party story into DEV-ready tasks |
| End-to-end tests | Tests that exercise a user or HTTP flow, not only a unit |
| Long-term support (LTS) | A released version we still patch. Clone a released Bug onto each supported line |
| PRD | BMad’s product-requirements workflow (bmad-prd). Overlay work uses Analysis (or Dev Open questions), on whichever spec location install chose |
| HALT | Stop. Do not continue the path |
| Open questions | Numbered reporter questions on the spec. Implement waits until this heading is None |
| ASK | Ask the human and wait. Do not guess |
| Knowledge | Distilled decisions in knowledge/ after the change request (context, choice, why). Later work starts from the spec, then these records |
| Org overlay | Committed _bmad/custom/bglad-ticket-mr.toml with hosts, squads, spec_store, and git_forge |
BMad’s own menus (Build, PRD, and so on) stay installed.