Module 1: BMM (Business Model Management)
The main product development module, designed for end-to-end project delivery following the BMad Method.
Phase 1 — Analysis
| Command |
Code |
What is this |
When to use |
/bmad-brainstorming |
BP |
Facilitated brainstorming using one or more structured techniques |
At the very start, when exploring ideas or when stuck generating them |
/bmad-bmm-market-research |
MR |
Competitive landscape, customer needs, and market trends analysis |
Before committing to a product direction; validate there's a market |
/bmad-bmm-domain-research |
DR |
Deep dive into industry domain, terminology, and subject matter |
When entering an unfamiliar domain or needing expert vocabulary |
/bmad-bmm-technical-research |
TR |
Technical feasibility study, architecture options, implementation approaches |
When tech choices are unclear or high-risk before planning begins |
/bmad-bmm-create-product-brief |
CB |
Guided session to crystallize the product idea into a brief |
After brainstorming; when you need to lock down "what are we building?" |
Phase 2 — Planning
| Command |
Code |
What is this |
When to use |
/bmad-bmm-create-prd |
CP |
[Required] Expert-facilitated session to produce the Product Requirements Document |
After analysis is done; the PRD gates entry into solutioning |
/bmad-bmm-validate-prd |
VP |
Checks that the PRD is comprehensive, lean, well-organized, and cohesive |
After creating the PRD; run before architecture to catch gaps early |
/bmad-bmm-edit-prd |
EP |
Improve and enhance an existing PRD |
When the PRD fails validation or stakeholders request changes |
/bmad-bmm-create-ux-design |
CU |
Guides the planning of UX patterns and design specifications |
Strongly recommended when a UI is a primary part of the product |
Phase 3 — Solutioning
| Command |
Code |
What is this |
When to use |
/bmad-bmm-create-architecture |
CA |
[Required] Guided workflow to document all technical decisions |
After PRD is approved; establishes the technical foundation before stories |
/bmad-bmm-create-epics-and-stories |
CE |
[Required] Breaks requirements into structured Epics and User Stories |
After architecture is set; creates the delivery roadmap |
/bmad-bmm-check-implementation-readiness |
IR |
[Required] Validates PRD, UX, Architecture, and Epics/Stories are all aligned |
Final gate before implementation; run with a high-quality LLM if available |
Phase 4 — Implementation
| Command |
Code |
What is this |
When to use |
/bmad-bmm-sprint-planning |
SP |
[Required] Generates the sprint plan from epics — the implementation kick-off |
Once readiness is confirmed; produces the plan all dev agents will follow |
/bmad-bmm-sprint-status |
SS |
Summarizes current sprint status and routes to the next workflow |
Anytime during a sprint to check progress |
/bmad-bmm-create-story |
CS |
[Required] Prepares the next story in the sprint plan with full context |
Start of every story cycle; run before Dev Story |
/bmad-bmm-dev-story |
DS |
[Required] Executes story implementation tasks and tests |
After story is created and validated; the main coding step |
/bmad-bmm-code-review |
CR |
Adversarial code review; routes back to Dev Story if issues found |
After Dev Story completes; the final checkpoint before moving to next story |
/bmad-bmm-retrospective |
ER |
Post-epic review to extract lessons learned and assess success |
Optional; at the end of each epic or when something went significantly wrong |
Anytime (BMM)
These BMM commands work at any point in the workflow:
| Command |
Code |
What is this |
When to use |
/bmad-bmm-document-project |
DP |
Analyzes an existing codebase and produces useful documentation |
For brownfield/legacy projects before starting new development |
/bmad-bmm-generate-project-context |
GPC |
Scans codebase and generates a lean LLM-optimized project-context.md
|
Essential for brownfield projects; run before any dev agent work |
/bmad-bmm-quick-spec |
QS |
Fast one-page tech spec for small changes or features |
Quick one-offs, small changes, brownfield additions; not for complex features |
/bmad-bmm-quick-dev |
QD |
Implement small tasks without full planning overhead |
Single ad-hoc tasks not already in the sprint plan |
/bmad-bmm-correct-course |
CC |
Navigates significant mid-sprint changes (may trigger PRD update, architecture redo, etc.) |
When a major blocker, pivot, or requirement change disrupts the current plan |
Agent-based BMM commands (load agent first, then invoke by code):
| Code |
Agent |
What is this |
When to use |
| WD |
📚 Paige (Tech Writer) — /bmad-bmm-tech-writer
|
Write a detailed document following documentation best practices |
Producing any formal documentation artifact |
| US |
📚 Paige (Tech Writer) |
Update documentation-standards.md with project-specific conventions |
When you discover missing or incorrect documentation conventions |
| MG |
📚 Paige (Tech Writer) |
Generate a Mermaid diagram from a description |
Visualizing flows, architecture, or sequences |
| VD |
📚 Paige (Tech Writer) |
Review a document against documentation standards |
Quality check before publishing or finalizing any document |
| EC |
📚 Paige (Tech Writer) |
Create clear technical explanations with examples and diagrams |
When a concept needs to be explained to the team or new members |
Module 2: CIS (Creative Innovation Suite)
Focused on creative thinking, innovation, and strategic problem solving. All CIS commands work anytime.
| Command |
Code |
What is this |
When to use |
/bmad-cis-innovation-strategy |
IS |
Identify disruption opportunities and architect business model innovation |
When exploring new business models or seeking competitive advantage |
/bmad-cis-problem-solving |
PS |
Apply systematic problem-solving methodologies to complex challenges |
When stuck on a difficult problem or needing a structured approach |
/bmad-cis-design-thinking |
DT |
Guide human-centered design using empathy-driven methodologies |
For user-centered design challenges or improving user experience |
/bmad-cis-brainstorming |
BS |
Facilitate brainstorming using proven structured techniques |
Early in ideation, or whenever idea generation is needed |
/bmad-cis-storytelling |
ST |
Craft compelling narratives using proven story frameworks |
When preparing persuasive communications, pitches, or story-driven content |
Module 3: Core (Universal Tools)
These commands work across all modules and all workflow phases. No module context required.
| Command |
Code |
What is this |
When to use |
/bmad-brainstorming |
BSP |
Generate diverse ideas through interactive techniques |
Any time creative input is needed |
/bmad-party-mode |
PM |
Orchestrate a multi-agent discussion with all installed agents |
When you want multiple agent perspectives or collaborative agent input |
/bmad-help |
BH |
Show the next recommended workflow steps based on context |
When you're unsure what to do next |
/bmad-index-docs |
ID |
Create a lightweight index of available docs for quick LLM scanning |
Before starting work in a docs-heavy folder so agents can navigate quickly |
/bmad-shard-doc |
SD |
Split a large document into smaller files organized by section |
When a doc exceeds ~500 lines and becomes hard to manage |
/bmad-editorial-review-prose |
EP |
Review prose for clarity, tone, and communication issues |
After drafting any written content to polish it |
/bmad-editorial-review-structure |
ES |
Propose cuts, reorganization, and simplification while preserving comprehension |
When a doc was assembled from multiple sub-processes or feels disorganized |
/bmad-review-adversarial-general |
AR |
Critically review content to find issues and weaknesses |
Quality assurance before finalizing any deliverable or document |
/bmad-review-edge-case-hunter |
ECH |
Walk every branch and boundary in code/content, report only unhandled edge cases |
Use alongside adversarial review for orthogonal, method-driven coverage |
Quick Cheat Sheet: Where am I? What do I run?
| Stage |
Must-run commands |
| Starting a new product |
/bmad-bmm-create-product-brief → /bmad-bmm-create-prd
|
| Planning tech |
/bmad-bmm-create-architecture → /bmad-bmm-create-epics-and-stories → /bmad-bmm-check-implementation-readiness
|
| Starting a sprint |
/bmad-bmm-sprint-planning |
| Each story cycle |
/bmad-bmm-create-story → /bmad-bmm-dev-story → /bmad-bmm-code-review
|
| Brownfield / existing codebase |
/bmad-bmm-generate-project-context first, then proceed |
| Quick one-off task |
/bmad-bmm-quick-spec → /bmad-bmm-quick-dev
|
| Something went wrong |
/bmad-bmm-correct-course |
| Don't know what's next |
/bmad-help |
This content is summarized by /bmad-help, the agent that helps us with anything about BMAD. You can also ask it for more details about BMAD usage.
Top comments (0)