Use for BMAD BMM (BMad Method) software-dev workflows: PRD, architecture, epics/stories, sprint planning, quick-spec/quick-dev, and lifecycle tracking. Trigger on 'BMM', 'BMad Method', or when users want structured planning/implementation via BMAD.
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.
send.sh --label bmad). Otherwise use the worker terminal.$bmad-help). Never send $$bmad-help.$bmad-help and list all available personas/agents and all BMM workflows.$bmad-help (top-to-bottom); if it changes, follow the latest list.brainstorm -> research -> create-product-brief.create-prd -> create-ux-design.create-architecture -> create-epics-and-stories -> check-implementation-readiness.sprint-planning -> create-story -> dev-story -> code-review -> correct-course -> retrospective.quick-spec -> quick-dev as a supplemental sanity pass (unless user opts out).document-project before Phase 4 (if uncertain, run it anyway).workflow-status (or equivalent) to confirm completion and next steps.$bmad-help and capture the full persona list and workflow list.brainstorm, research, create-product-brief.create-prd, create-ux-design.create-architecture, create-epics-and-stories, check-implementation-readiness.document-project (if uncertain, run it).sprint-planning, create-story, dev-story, code-review, correct-course, retrospective.quick-spec, quick-dev (unless user opts out).workflow-status.send.sh.$bmad-help -> choose next workflow -> $bmad:bmm:workflows:create-prd.references/workflow-map.mdreferences/track-selection.md