BMAD BMM (BMad Method)
Overview
Drive the BMM lifecycle (analysis -> planning -> solutioning -> implementation) via the worker terminal. Use $bmad-help or workflow-status to determine the next workflow, then run the appropriate $bmad:bmm:workflows:<id> (or tool-equivalent) command in the worker.
Default mode is EXHAUSTIVE. Unless the user explicitly asks for a lighter path, run the BMM workflows exhaustively: consult every BMAD persona, run every workflow in the map, and ensure all optional stages execute.
Non-negotiable execution rules
- Run all BMAD BMM workflows in the worker or dedicated BMAD window, never locally in the controller session.
- If a BMAD window exists, send commands there (use
send.sh --label bmad). Otherwise use the worker terminal.
- Do not manually draft PRD, architecture, epics, or stories in the controller when a BMAD workflow can generate them.
- Always load the BMAD agent persona and follow its menu items before running workflows.
- Do not forward the user's request verbatim to the worker. First read the relevant files locally, then translate the request into concrete BMAD menu steps and commands for the worker.
- Use BMAD commands with a single leading dollar sign (e.g.
$bmad-help). Never send $$bmad-help.
- If the BMM workflow requires it, start by loading the SM agent.
- Default to EXHAUSTIVE unless the user explicitly opts out.
- EXHAUSTIVE = consult every available BMAD persona/agent, and run every workflow in the BMM map, including all optional stages.
- If a workflow is optional or conditional and its applicability is unclear, run it anyway and note assumptions in the artifacts.
- Do not stop after any single stage; continue until all workflows are complete.
- Advanced Elicitation is mandatory. If prompted for elicitation depth or mode, always choose Advanced Elicitation. If a standalone "Advanced Elicitation" workflow/menu item exists, run it before Phase 1 and again at each major gate (post-PRD, post-architecture, pre-implementation).
Workflow
- Determine execution mode (default: EXHAUSTIVE)
- If the user explicitly requests quick/small scope, follow that request.
- Otherwise run EXHAUSTIVE and do not short-circuit on scope.
- Enumerate personas and workflows
- In the worker, run
$bmad-help and list all available personas/agents and all BMM workflows.
- Consult every persona before Phase 1, and again at key gates (post-PRD, post-architecture, pre-implementation).
- Use the persona order shown by
$bmad-help (top-to-bottom); if it changes, follow the latest list.
- When elicitation depth/mode is offered, select Advanced Elicitation every time.
- Run the full workflow map (EXHAUSTIVE)
- Phase 1 (optional by default):
brainstorm -> research -> create-product-brief.
- Phase 2:
create-prd -> create-ux-design.
- Phase 3:
create-architecture -> create-epics-and-stories -> check-implementation-readiness.
- Phase 4:
sprint-planning -> create-story -> dev-story -> code-review -> correct-course -> retrospective.
- Quick Flow: also run
quick-spec -> quick-dev as a supplemental sanity pass (unless user opts out).
- Brownfield: if the repo is existing or docs are missing, run
document-project before Phase 4 (if uncertain, run it anyway).
- Enterprise extensions: if the menu exposes security, DevOps, or test-strategy workflows, run them as well.
- Track progress
- After each workflow, run
workflow-status (or equivalent) to confirm completion and next steps.
Exhaustive Checklist (default)
- Run
$bmad-help and capture the full persona list and workflow list.
- Consult every persona once in the order shown.
- Run Advanced Elicitation (if offered as a workflow or mode).
- Phase 1:
brainstorm, research, create-product-brief.
- Consult every persona again (same order).
- Run Advanced Elicitation again if offered.
- Phase 2:
create-prd, create-ux-design.
- Consult every persona again (same order).
- Run Advanced Elicitation again if offered.
- Phase 3:
create-architecture, create-epics-and-stories, check-implementation-readiness.
- Consult every persona again (same order).
- Run Advanced Elicitation again if offered.
- Brownfield:
document-project (if uncertain, run it).
- Phase 4:
sprint-planning, create-story, dev-story, code-review, correct-course, retrospective.
- Quick Flow sanity pass:
quick-spec, quick-dev (unless user opts out).
- Enterprise extensions: run any security, DevOps, or test-strategy workflows exposed in the menu.
- After each workflow, run
workflow-status.
Worker Command Pattern
- Always send BMAD commands to the worker via
send.sh.
- Example:
$bmad-help -> choose next workflow -> $bmad:bmm:workflows:create-prd.
References
references/workflow-map.md
references/track-selection.md
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: dickymoore-macs-bmad-bmm3description: BMAD BMM (BMad Method)4---56# BMAD BMM (BMad Method)78## Overview9Drive the BMM lifecycle (analysis -> planning -> solutioning -> implementation) via the worker terminal. Use `$bmad-help` or `workflow-status` to determine the next workflow, then run the appropriate `$bmad:bmm:workflows:<id>` (or tool-equivalent) command in the worker.1011**Default mode is EXHAUSTIVE.** Unless the user explicitly asks for a lighter path, run the BMM workflows exhaustively: consult every BMAD persona, run every workflow in the map, and ensure all optional stages execute.1213## Non-negotiable execution rules14- Run all BMAD BMM workflows in the worker or dedicated BMAD window, never locally in the controller session.15- If a BMAD window exists, send commands there (use `send.sh --label bmad`). Otherwise use the worker terminal.16- Do not manually draft PRD, architecture, epics, or stories in the controller when a BMAD workflow can generate them.17- Always load the BMAD agent persona and follow its menu items before running workflows.18- Do not forward the user's request verbatim to the worker. First read the relevant files locally, then translate the request into concrete BMAD menu steps and commands for the worker.19- Use BMAD commands with a single leading dollar sign (e.g. `$bmad-help`). Never send `$$bmad-help`.20- If the BMM workflow requires it, start by loading the **SM agent**.21- Default to **EXHAUSTIVE** unless the user explicitly opts out.22- **EXHAUSTIVE =** consult **every** available BMAD persona/agent, and run **every** workflow in the BMM map, including all optional stages.23- If a workflow is optional or conditional and its applicability is unclear, **run it anyway** and note assumptions in the artifacts.24- Do not stop after any single stage; continue until all workflows are complete.25- **Advanced Elicitation is mandatory.** If prompted for elicitation depth or mode, always choose **Advanced Elicitation**. If a standalone "Advanced Elicitation" workflow/menu item exists, run it before Phase 1 and again at each major gate (post-PRD, post-architecture, pre-implementation).2627## Workflow28291) Determine execution mode (default: **EXHAUSTIVE**)30- If the user explicitly requests quick/small scope, follow that request.31- Otherwise run **EXHAUSTIVE** and do not short-circuit on scope.32332) Enumerate personas and workflows34- In the worker, run `$bmad-help` and list **all** available personas/agents and **all** BMM workflows.35- Consult **every** persona before Phase 1, and again at key gates (post-PRD, post-architecture, pre-implementation).36- Use the persona order shown by `$bmad-help` (top-to-bottom); if it changes, follow the latest list.37- When elicitation depth/mode is offered, select **Advanced Elicitation** every time.38393) Run the full workflow map (EXHAUSTIVE)40- **Phase 1 (optional by default):** `brainstorm` -> `research` -> `create-product-brief`.41- **Phase 2:** `create-prd` -> `create-ux-design`.42- **Phase 3:** `create-architecture` -> `create-epics-and-stories` -> `check-implementation-readiness`.43- **Phase 4:** `sprint-planning` -> `create-story` -> `dev-story` -> `code-review` -> `correct-course` -> `retrospective`.44- **Quick Flow:** also run `quick-spec` -> `quick-dev` as a supplemental sanity pass (unless user opts out).45- **Brownfield:** if the repo is existing or docs are missing, run `document-project` before Phase 4 (if uncertain, run it anyway).46- **Enterprise extensions:** if the menu exposes security, DevOps, or test-strategy workflows, run them as well.47484) Track progress49- After each workflow, run `workflow-status` (or equivalent) to confirm completion and next steps.5051## Exhaustive Checklist (default)521) Run `$bmad-help` and capture the full persona list and workflow list.532) Consult every persona once in the order shown.543) Run **Advanced Elicitation** (if offered as a workflow or mode).554) Phase 1: `brainstorm`, `research`, `create-product-brief`.565) Consult every persona again (same order).576) Run **Advanced Elicitation** again if offered.587) Phase 2: `create-prd`, `create-ux-design`.598) Consult every persona again (same order).609) Run **Advanced Elicitation** again if offered.6110) Phase 3: `create-architecture`, `create-epics-and-stories`, `check-implementation-readiness`.6211) Consult every persona again (same order).6312) Run **Advanced Elicitation** again if offered.6413) Brownfield: `document-project` (if uncertain, run it).6514) Phase 4: `sprint-planning`, `create-story`, `dev-story`, `code-review`, `correct-course`, `retrospective`.6615) Quick Flow sanity pass: `quick-spec`, `quick-dev` (unless user opts out).6716) Enterprise extensions: run any security, DevOps, or test-strategy workflows exposed in the menu.6817) After each workflow, run `workflow-status`.6970## Worker Command Pattern71- Always send BMAD commands to the worker via `send.sh`.72- Example: `$bmad-help` -> choose next workflow -> `$bmad:bmm:workflows:create-prd`.7374## References75- `references/workflow-map.md`76- `references/track-selection.md`7778---79> Converted and distributed by [TomeVault](https://tomevault.io/claim/dickymoore) — claim your Tome and manage your conversions.80<!-- tomevault:4.0:skill_md:2026-04-14 -->