Words and menu codes

Help-menu codes are the same words as the step, shortened:

Menu	Say this	Skill
SO	Solo	bglad-solo
TE	Team	bglad-team
DS	Design	bglad-architecture
DEV	Dev / implement	bglad-dev
RV	Review	bglad-review
QA	Tests / QA	bglad-qa
MR	Ticket, merge request, or pull request	bglad-ticket-mr
NOTE	Knowledge note	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.

Pick one path. Solo is not “Team with one person skipping steps.” Team still runs review and tests even if the same person wears those hats.

Other words you will see

Word	Meaning
Overlay	Extra skills installed on top of BMad. BMad itself stays as shipped
Override	Sparse _bmad/custom/ TOML (or a squad table) that changes defaults. See Override defaults
Spec location	Where Solo/Team keep Problem / Acceptance / Design / Test notes: 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	The person who starts Team: what we are building and what done looks like
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). Solo or Team replace that for overlay work, on whichever spec location install chose
HALT	Stop. Do not continue the path
ASK	Ask the human and wait. Do not guess
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.