ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

docs: update terminology from commands to skills across all documentation 

Align documentation with the skills-based architecture migration by
replacing references to "commands", "slash commands", and legacy command
names with the new "skills" terminology and skill names.
This commit is contained in:
Alex Verkhovsky 2026-03-07 15:41:03 -07:00
parent ec973ebcf3
commit 986477f6e2
19 changed files with 211 additions and 204 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/_STYLE_GUIDE.md
View File

@ -59,13 +59,13 @@ Critical warnings only — data loss, security issues
| 2 | Planning | Requirements — PRD or tech-spec *(required)* | | 2 | Planning | Requirements — PRD or tech-spec *(required)* |
``` ```
**Commands:** **Skills:**
```md ```md
| Command | Agent | Purpose | | Skill | Agent | Purpose |
| ------------ | ------- | ------------------------------------ | | ------------ | ------- | ------------------------------------ |
| `brainstorm` | Analyst | Brainstorm a new project | | `bmad-brainstorming` | Analyst | Brainstorm a new project |
| `prd` | PM | Create Product Requirements Document | | `bmad-create-prd` | PM | Create Product Requirements Document |
``` ```
## Folder Structure Blocks ## Folder Structure Blocks
@ -99,7 +99,7 @@ your-project/
9. Step 2: [Second Major Task] 9. Step 2: [Second Major Task]
10. Step 3: [Third Major Task] 10. Step 3: [Third Major Task]
11. What You've Accomplished (summary + folder structure) 11. What You've Accomplished (summary + folder structure)
12. Quick Reference (commands table) 12. Quick Reference (skills table)
13. Common Questions (FAQ format) 13. Common Questions (FAQ format)
14. Getting Help (community links) 14. Getting Help (community links)
15. Key Takeaways (tip admonition) 15. Key Takeaways (tip admonition)
@ -111,7 +111,7 @@ your-project/
- [ ] "What You'll Learn" section present - [ ] "What You'll Learn" section present
- [ ] Prerequisites in admonition - [ ] Prerequisites in admonition
- [ ] Quick Path TL;DR admonition at top - [ ] Quick Path TL;DR admonition at top
- [ ] Tables for phases, commands, agents - [ ] Tables for phases, skills, agents
- [ ] "What You've Accomplished" section present - [ ] "What You've Accomplished" section present
- [ ] Quick Reference table present - [ ] Quick Reference table present
- [ ] Common Questions section present - [ ] Common Questions section present
@ -243,7 +243,7 @@ your-project/
1. Title + Hook 1. Title + Hook
2. Items (## for each item) 2. Items (## for each item)
- Brief description (one sentence) - Brief description (one sentence)
- **Commands:** or **Key Info:** as flat list - **Skills:** or **Key Info:** as flat list
3. Universal/Shared (## section) (optional) 3. Universal/Shared (## section) (optional)
``` ```
@ -252,7 +252,7 @@ your-project/
```text ```text
1. Title + Hook (one sentence purpose) 1. Title + Hook (one sentence purpose)
2. Quick Facts (optional note admonition) 2. Quick Facts (optional note admonition)
- Module, Command, Input, Output as list - Module, Skill, Input, Output as list
3. Purpose/Overview (## section) 3. Purpose/Overview (## section)
4. How to Invoke (code block) 4. How to Invoke (code block)
5. Key Sections (## for each aspect) 5. Key Sections (## for each aspect)
@ -280,7 +280,7 @@ your-project/
- Diagram or table showing organization - Diagram or table showing organization
3. Major Sections (## for each phase/category) 3. Major Sections (## for each phase/category)
- Items (### for each item) - Items (### for each item)
- Standardized fields: Command, Agent, Input, Output, Description - Standardized fields: Skill, Agent, Input, Output, Description
4. Next Steps (optional) 4. Next Steps (optional)
``` ```
@ -353,7 +353,7 @@ Only for BMad Method and Enterprise tracks. Quick Flow skips to implementation.
### Can I change my plan later? ### Can I change my plan later?
Yes. The SM agent has a `correct-course` workflow for handling scope changes. Yes. The SM agent has a `bmad-correct-course` workflow for handling scope changes.
**Have a question not answered here?** [Open an issue](...) or ask in [Discord](...). **Have a question not answered here?** [Open an issue](...) or ask in [Discord](...).
``` ```

2
docs/explanation/brainstorming.md
View File

@ -9,7 +9,7 @@ Unlock your creativity through guided exploration.
## What is Brainstorming? ## What is Brainstorming?
Run `brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges. Run `bmad-brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges.
**Good for:** **Good for:**

2
docs/explanation/party-mode.md
View File

@ -9,7 +9,7 @@ Get all your AI agents in one conversation.
## What is Party Mode? ## What is Party Mode?
Run `party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas. Run `bmad-party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas.
The conversation continues as long as you want. Ask follow-ups, push back on answers, redirect the discussion - it's a real back-and-forth with your agents until you're done. The conversation continues as long as you want. Ask follow-ups, push back on answers, redirect the discussion - it's a real back-and-forth with your agents until you're done.

2
docs/explanation/preventing-agent-conflicts.md
View File

@ -108,5 +108,5 @@ Common decisions that prevent conflicts:
- Document decisions that cross epic boundaries - Document decisions that cross epic boundaries
- Focus on conflict-prone areas - Focus on conflict-prone areas
- Update architecture as you learn - Update architecture as you learn
- Use `correct-course` for significant changes - Use `bmad-correct-course` for significant changes
::: :::

30
docs/explanation/project-context.md
View File

@ -21,12 +21,12 @@ The `project-context.md` file solves this by documenting what agents need to kno
Every implementation workflow automatically loads `project-context.md` if it exists. The architect workflow also loads it to respect your technical preferences when designing the architecture. Every implementation workflow automatically loads `project-context.md` if it exists. The architect workflow also loads it to respect your technical preferences when designing the architecture.
**Loaded by these workflows:** **Loaded by these workflows:**
- `create-architecture` — respects technical preferences during solutioning - `bmad-create-architecture` — respects technical preferences during solutioning
- `create-story` — informs story creation with project patterns - `bmad-create-story` — informs story creation with project patterns
- `dev-story` — guides implementation decisions - `bmad-dev-story` — guides implementation decisions
- `code-review` — validates against project standards - `bmad-code-review` — validates against project standards
- `quick-dev` — applies patterns when implementing tech-specs - `bmad-quick-dev` — applies patterns when implementing tech-specs
- `sprint-planning`, `retrospective`, `correct-course` — provides project-wide context - `bmad-sprint-planning`, `bmad-retrospective`, `bmad-correct-course` — provides project-wide context
## When to Create It ## When to Create It
@ -34,10 +34,10 @@ The `project-context.md` file is useful at any stage of a project:
| Scenario | When to Create | Purpose | | Scenario | When to Create | Purpose |
|----------|----------------|---------| |----------|----------------|---------|
| **New project, before architecture** | Manually, before `create-architecture` | Document your technical preferences so the architect respects them | | **New project, before architecture** | Manually, before `bmad-create-architecture` | Document your technical preferences so the architect respects them |
| **New project, after architecture** | Via `generate-project-context` or manually | Capture architecture decisions for implementation agents | | **New project, after architecture** | Via `bmad-generate-project-context` or manually | Capture architecture decisions for implementation agents |
| **Existing project** | Via `generate-project-context` | Discover existing patterns so agents follow established conventions | | **Existing project** | Via `bmad-generate-project-context` | Discover existing patterns so agents follow established conventions |
| **Quick Flow project** | Before or during `quick-dev` | Ensure quick implementation respects your patterns | | **Quick Flow project** | Before or during `bmad-quick-dev` | Ensure quick implementation respects your patterns |
:::tip[Recommended] :::tip[Recommended]
For new projects, create it manually before architecture if you have strong technical preferences. Otherwise, generate it after architecture to capture those decisions. For new projects, create it manually before architecture if you have strong technical preferences. Otherwise, generate it after architecture to capture those decisions.
@ -107,20 +107,20 @@ Edit it with your technology stack and implementation rules. The architect and i
### Generate After Architecture ### Generate After Architecture
Run the `generate-project-context` workflow after completing your architecture: Run the `bmad-generate-project-context` workflow after completing your architecture:
```bash ```bash
/bmad-bmm-generate-project-context bmad-generate-project-context
``` ```
This scans your architecture document and project files to generate a context file capturing the decisions made. This scans your architecture document and project files to generate a context file capturing the decisions made.
### Generate for Existing Projects ### Generate for Existing Projects
For existing projects, run `generate-project-context` to discover existing patterns: For existing projects, run `bmad-generate-project-context` to discover existing patterns:
```bash ```bash
/bmad-bmm-generate-project-context bmad-generate-project-context
``` ```
The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine. The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine.
@ -150,7 +150,7 @@ The `project-context.md` file is a living document. Update it when:
- Patterns evolve during implementation - Patterns evolve during implementation
- You identify gaps from agent behavior - You identify gaps from agent behavior
You can edit it manually at any time, or re-run `generate-project-context` to update it after significant changes. You can edit it manually at any time, or re-run `bmad-generate-project-context` to update it after significant changes.
:::note[File Location] :::note[File Location]
The default location is `_bmad-output/project-context.md`. Workflows search for it there, and also check `**/project-context.md` anywhere in your project. The default location is `_bmad-output/project-context.md`. Workflows search for it there, and also check `**/project-context.md` anywhere in your project.

18
docs/explanation/quick-flow.md
View File

@ -5,7 +5,7 @@ sidebar:
order: 1 order: 1
--- ---
Skip the ceremony. Quick Flow takes you from idea to working code in two commands - no Product Brief, no PRD, no Architecture doc. Skip the ceremony. Quick Flow takes you from idea to working code in two skills - no Product Brief, no PRD, no Architecture doc.
## When to Use It ## When to Use It
@ -23,16 +23,16 @@ Skip the ceremony. Quick Flow takes you from idea to working code in two command
- Anything where requirements are unclear or contested - Anything where requirements are unclear or contested
:::caution[Scope Creep] :::caution[Scope Creep]
If you start a Quick Flow and realize the scope is bigger than expected, `quick-dev` will detect this and offer to escalate. You can switch to a full PRD workflow at any point without losing your work. If you start a Quick Flow and realize the scope is bigger than expected, `bmad-quick-dev` will detect this and offer to escalate. You can switch to a full PRD workflow at any point without losing your work.
::: :::
## How It Works ## How It Works
Quick Flow has two commands, each backed by a structured workflow. You can run them together or independently. Quick Flow has two skills, each backed by a structured workflow. You can run them together or independently.
### quick-spec: Plan ### quick-spec: Plan
Run `quick-spec` and Barry (the Quick Flow agent) walks you through a conversational discovery process: Run `bmad-quick-spec` and Barry (the Quick Flow agent) walks you through a conversational discovery process:
1. **Understand** - You describe what you want to build. Barry scans the codebase to ask informed questions, then captures a problem statement, solution approach, and scope boundaries. 1. **Understand** - You describe what you want to build. Barry scans the codebase to ask informed questions, then captures a problem statement, solution approach, and scope boundaries.
2. **Investigate** - Barry reads relevant files, maps code patterns, identifies files to modify, and documents the technical context. 2. **Investigate** - Barry reads relevant files, maps code patterns, identifies files to modify, and documents the technical context.
@ -43,15 +43,15 @@ The output is a `tech-spec-{slug}.md` file saved to your project's implementatio
### quick-dev: Build ### quick-dev: Build
Run `quick-dev` and Barry implements the work. It operates in two modes: Run `bmad-quick-dev` and Barry implements the work. It operates in two modes:
- **Tech-spec mode** - Point it at a spec file (`quick-dev tech-spec-auth.md`) and it executes every task in order, writes tests, and verifies acceptance criteria. - **Tech-spec mode** - Point it at a spec file (`quick-dev tech-spec-auth.md`) and it executes every task in order, writes tests, and verifies acceptance criteria.
- **Direct mode** - Give it instructions directly (`quick-dev "refactor the auth middleware"`) and it gathers context, builds a mental plan, and executes. - **Direct mode** - Give it instructions directly (`quick-dev "refactor the auth middleware"`) and it gathers context, builds a mental plan, and executes.
After implementation, `quick-dev` runs a self-check audit against all tasks and acceptance criteria, then triggers an adversarial code review of the diff. Findings are presented for you to resolve before wrapping up. After implementation, `bmad-quick-dev` runs a self-check audit against all tasks and acceptance criteria, then triggers an adversarial code review of the diff. Findings are presented for you to resolve before wrapping up.
:::tip[Fresh Context] :::tip[Fresh Context]
For best results, run `quick-dev` in a new conversation after finishing `quick-spec`. This gives the implementation agent clean context focused solely on building. For best results, run `bmad-quick-dev` in a new conversation after finishing `bmad-quick-spec`. This gives the implementation agent clean context focused solely on building.
::: :::
## What Quick Flow Skips ## What Quick Flow Skips
@ -65,9 +65,9 @@ The full BMad Method produces a Product Brief, PRD, Architecture doc, and Epic/S
## Escalating to Full BMad Method ## Escalating to Full BMad Method
Quick Flow includes built-in guardrails for scope detection. When you run `quick-dev` with a direct request, it evaluates signals like multi-component mentions, system-level language, and uncertainty about approach. If it detects the work is bigger than a quick flow: Quick Flow includes built-in guardrails for scope detection. When you run `bmad-quick-dev` with a direct request, it evaluates signals like multi-component mentions, system-level language, and uncertainty about approach. If it detects the work is bigger than a quick flow:
- **Light escalation** - Recommends running `quick-spec` first to create a plan - **Light escalation** - Recommends running `bmad-quick-spec` first to create a plan
- **Heavy escalation** - Recommends switching to the full BMad Method PRD process - **Heavy escalation** - Recommends switching to the full BMad Method PRD process
You can also escalate manually at any time. Your tech-spec work carries forward - it becomes input for the broader planning process rather than being discarded. You can also escalate manually at any time. Your tech-spec work carries forward - it becomes input for the broader planning process rather than being discarded.

14
docs/how-to/established-projects.md
View File

@ -32,7 +32,7 @@ Generate `project-context.md` to capture your existing codebase patterns and con
Run the generate project context workflow: Run the generate project context workflow:
```bash ```bash
/bmad-bmm-generate-project-context bmad-generate-project-context
``` ```
This scans your codebase to identify: This scans your codebase to identify:
@ -55,22 +55,22 @@ Your `docs/` folder should contain succinct, well-organized documentation that a
- Architecture - Architecture
- Any other relevant project information - Any other relevant project information
For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state. For complex projects, consider using the `bmad-document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
## Step 3: Get Help ## Step 3: Get Help
### BMad-Help: Your Starting Point ### BMad-Help: Your Starting Point
**Run `/bmad-help` anytime you're unsure what to do next.** This intelligent guide: **Run `bmad-help` anytime you're unsure what to do next.** This intelligent guide:
- Inspects your project to see what's already been done - Inspects your project to see what's already been done
- Shows options based on your installed modules - Shows options based on your installed modules
- Understands natural language queries - Understands natural language queries
``` ```
/bmad-help I have an existing Rails app, where should I start? bmad-help I have an existing Rails app, where should I start?
/bmad-help What's the difference between quick-flow and full method? bmad-help What's the difference between quick-flow and full method?
/bmad-help Show me what workflows are available bmad-help Show me what workflows are available
``` ```
BMad-Help also **automatically runs at the end of every workflow**, providing clear guidance on exactly what to do next. BMad-Help also **automatically runs at the end of every workflow**, providing clear guidance on exactly what to do next.
@ -81,7 +81,7 @@ You have two primary options depending on the scope of changes:
| Scope | Recommended Approach | | Scope | Recommended Approach |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| **Small updates or additions** | Use `quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad Method is likely overkill. | | **Small updates or additions** | Use `bmad-quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad Method is likely overkill. |
| **Major changes or additions** | Start with the BMad Method, applying as much or as little rigor as needed. | | **Major changes or additions** | Start with the BMad Method, applying as much or as little rigor as needed. |
### During PRD Creation ### During PRD Creation

4
docs/how-to/get-answers-about-bmad.md
View File

@ -18,7 +18,7 @@ BMad-Help is more than a lookup tool — it:
### How to Use BMad-Help ### How to Use BMad-Help
Run it with just the slash command: Run it with just the skill name:
``` ```
/bmad-help /bmad-help
@ -81,7 +81,7 @@ https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt
:::note[Example] :::note[Example]
**Q:** "Tell me the fastest way to build something with BMad" **Q:** "Tell me the fastest way to build something with BMad"
**A:** Use Quick Flow: Run `quick-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases. **A:** Use Quick Flow: Run `bmad-quick-spec` to write a technical specification, then `bmad-quick-dev` to implement it—skipping the full planning phases.
::: :::
## What You Get ## What You Get

22
docs/how-to/install-bmad.md
View File

@ -51,7 +51,11 @@ Pick which AI tools you use:
- Cursor - Cursor
- Others - Others
Each tool has its own way of integrating commands. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them. Each tool has its own way of integrating skills. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them.
:::note[Enabling Skills]
Some platforms require skills to be explicitly enabled in settings before they appear. If you install BMad and don't see the skills, check your platform's settings or ask your AI assistant how to enable skills.
:::
### 4. Choose Modules ### 4. Choose Modules
@ -71,13 +75,19 @@ your-project/
│ ├── core/ # Required core module │ ├── core/ # Required core module
│ └── ... │ └── ...
├── _bmad-output/ # Generated artifacts ├── _bmad-output/ # Generated artifacts
├── .claude/ # Claude Code commands (if using Claude Code) ├── .claude/ # Claude Code skills (if using Claude Code)
└── .kiro/ # Kiro steering files (if using Kiro) │ └── skills/
│ ├── bmad-help/
│ ├── bmad-persona/
│ └── ...
└── .cursor/ # Cursor skills (if using Cursor)
└── skills/
└── ...
``` ```
## Verify Installation ## Verify Installation
Run `/bmad-help` to verify everything works and see what to do next. Run `bmad-help` to verify everything works and see what to do next.
**BMad-Help is your intelligent guide** that will: **BMad-Help is your intelligent guide** that will:
- Confirm your installation is working - Confirm your installation is working
@ -86,8 +96,8 @@ Run `/bmad-help` to verify everything works and see what to do next.
You can also ask it questions: You can also ask it questions:
``` ```
/bmad-help I just installed, what should I do first? bmad-help I just installed, what should I do first?
/bmad-help What are my options for a SaaS project? bmad-help What are my options for a SaaS project?
``` ```
## Troubleshooting ## Troubleshooting

4
docs/how-to/project-context.md
View File

@ -77,7 +77,7 @@ sections_completed: ['technology_stack', 'critical_rules']
Run the workflow in a fresh chat: Run the workflow in a fresh chat:
```bash ```bash
/bmad-bmm-generate-project-context bmad-generate-project-context
``` ```
The workflow scans your architecture document and project files to generate a context file capturing the decisions made. The workflow scans your architecture document and project files to generate a context file capturing the decisions made.
@ -87,7 +87,7 @@ The workflow scans your architecture document and project files to generate a co
For existing projects, run: For existing projects, run:
```bash ```bash
/bmad-bmm-generate-project-context bmad-generate-project-context
``` ```
The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine. The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine.

10
docs/how-to/quick-fixes.md
View File

@ -30,18 +30,18 @@ If you are unsure, start with the DEV agent. You can always escalate to Quick Fl
## Steps ## Steps
### 1. Load the DEV Agent ### 1. Invoke the DEV Agent
Start a **fresh chat** in your AI IDE and load the DEV agent with its slash command: Start a **fresh chat** in your AI IDE and invoke the DEV agent skill:
```text ```text
/bmad-agent-bmm-dev bmad-dev
``` ```
This loads the agent's persona and capabilities into the session. If you decide you need Quick Flow instead, load the **Quick Flow Solo Dev** agent in a fresh chat: This loads the agent's persona and capabilities into the session. If you decide you need Quick Flow instead, invoke the **Quick Flow Solo Dev** agent skill in a fresh chat:
```text ```text
/bmad-agent-bmm-quick-flow-solo-dev bmad-quick-flow-solo-dev
``` ```
Once the Solo Dev agent is loaded, describe your change and ask it to create a **quick-spec**. The agent drafts a lightweight spec capturing what you want to change and how. After you approve the quick-spec, tell the agent to start the **Quick Flow dev cycle** -- it will implement the change, run tests, and perform a self-review, all guided by the spec you just approved. Once the Solo Dev agent is loaded, describe your change and ask it to create a **quick-spec**. The agent drafts a lightweight spec capturing what you want to change and how. After you approve the quick-spec, tell the agent to start the **Quick Flow dev cycle** -- it will implement the change, run tests, and perform a self-review, all guided by the spec you just approved.

2
docs/how-to/shard-large-documents.md
View File

@ -5,7 +5,7 @@ sidebar:
order: 8 order: 8
--- ---
Use the `shard-doc` tool if you need to split large markdown files into smaller, organized files for better context management. Use the `bmad-shard-doc` tool if you need to split large markdown files into smaller, organized files for better context management.
:::caution[Deprecated] :::caution[Deprecated]
This is no longer recommended, and soon with updated workflows and most major LLMs and tools supporting subprocesses this will be unnecessary. This is no longer recommended, and soon with updated workflows and most major LLMs and tools supporting subprocesses this will be unnecessary.

13
docs/how-to/upgrade-to-v6.md
View File

@ -33,12 +33,15 @@ When v4 is detected, you can:
If you named your bmad method folder something else - you will need to manually remove the folder yourself. If you named your bmad method folder something else - you will need to manually remove the folder yourself.
### 3. Clean Up IDE Commands ### 3. Clean Up IDE Skills
Manually remove legacy v4 IDE commands - for example if you have claude, look for any nested folders that start with bmad and remove them: Manually remove legacy v4 IDE commands/skills - for example if you have Claude Code, look for any nested folders that start with bmad and remove them:
- `.claude/commands/BMad/agents` - `.claude/commands/`
- `.claude/commands/BMad/tasks`
The new v6 skills are installed to:
- `.claude/skills/`
### 4. Migrate Planning Artifacts ### 4. Migrate Planning Artifacts
@ -58,7 +61,7 @@ If you have stories created or implemented:
1. Complete the v6 installation 1. Complete the v6 installation
2. Place `epics.md` or `epics/epic*.md` in `_bmad-output/planning-artifacts/` 2. Place `epics.md` or `epics/epic*.md` in `_bmad-output/planning-artifacts/`
3. Run the Scrum Master's `sprint-planning` workflow 3. Run the Scrum Master's `bmad-sprint-planning` workflow
4. Tell the SM which epics/stories are already complete 4. Tell the SM which epics/stories are already complete
## What You Get ## What You Get

2
docs/index.md
View File

@ -19,7 +19,7 @@ The fastest way to understand BMad is to try it.
- **[Workflow Map](./reference/workflow-map.md)** — Visual overview of BMM phases, workflows, and context management - **[Workflow Map](./reference/workflow-map.md)** — Visual overview of BMM phases, workflows, and context management
:::tip[Just Want to Dive In?] :::tip[Just Want to Dive In?]
Install BMad and run `/bmad-help` — it will guide you through everything based on your project and installed modules. Install BMad and use the `bmad-help` skill — it will guide you through everything based on your project and installed modules.
::: :::
## How to Use These Docs ## How to Use These Docs

28
docs/reference/agents.md
View File

@ -1,28 +1,28 @@
--- ---
title: Agents title: Agents
description: Default BMM agents with their menu triggers and primary workflows description: Default BMM agents with their skill IDs, menu triggers, and primary workflows
sidebar: sidebar:
order: 2 order: 2
--- ---
## Default Agents ## Default Agents
This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their menu triggers and primary workflows. This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their skill IDs, menu triggers, and primary workflows. Each agent is invoked as a skill.
## Notes ## Notes
- Each agent is available as a skill, generated by the installer. The skill ID (e.g., `bmad-dev`) is used to invoke the agent.
- Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu. - Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu.
- Slash commands are generated separately. See [Commands](./commands.md) for the slash command list and where they are defined.
- QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module. - QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
| Agent | Triggers | Primary workflows | | Agent | Skill ID | Triggers | Primary workflows |
| --------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- | | --------------------------- | -------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
| Analyst (Mary) | `BP`, `RS`, `CB`, `DP` | Brainstorm Project, Research, Create Brief, Document Project | | Analyst (Mary) | `bmad-analyst` | `BP`, `RS`, `CB`, `DP` | Brainstorm Project, Research, Create Brief, Document Project |
| Product Manager (John) | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course | | Product Manager (John) | `bmad-pm` | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course |
| Architect (Winston) | `CA`, `IR` | Create Architecture, Implementation Readiness | | Architect (Winston) | `bmad-architect` | `CA`, `IR` | Create Architecture, Implementation Readiness |
| Scrum Master (Bob) | `SP`, `CS`, `ER`, `CC` | Sprint Planning, Create Story, Epic Retrospective, Correct Course | | Scrum Master (Bob) | `bmad-sm` | `SP`, `CS`, `ER`, `CC` | Sprint Planning, Create Story, Epic Retrospective, Correct Course |
| Developer (Amelia) | `DS`, `CR` | Dev Story, Code Review | | Developer (Amelia) | `bmad-dev` | `DS`, `CR` | Dev Story, Code Review |
| QA Engineer (Quinn) | `QA` | Automate (generate tests for existing features) | | QA Engineer (Quinn) | `bmad-qa` | `QA` | Automate (generate tests for existing features) |
| Quick Flow Solo Dev (Barry) | `QS`, `QD`, `CR` | Quick Spec, Quick Dev, Code Review | | Quick Flow Solo Dev (Barry) | `bmad-master` | `QS`, `QD`, `CR` | Quick Spec, Quick Dev, Code Review |
| UX Designer (Sally) | `CU` | Create UX Design | | UX Designer (Sally) | `bmad-ux-designer` | `CU` | Create UX Design |
| Technical Writer (Paige) | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept | | Technical Writer (Paige) | `bmad-tech-writer` | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |

134
docs/reference/commands.md
View File

@ -1,111 +1,113 @@
--- ---
title: Commands title: Skills
description: Reference for BMad slash commands — what they are, how they work, and where to find them. description: Reference for BMad skills — what they are, how they work, and where to find them.
sidebar: sidebar:
order: 3 order: 3
--- ---
Slash commands are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep commands in sync (see [Troubleshooting](#troubleshooting)). Skills are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep skills in sync (see [Troubleshooting](#troubleshooting)).
## Commands vs. Agent Menu Triggers ## Skills vs. Agent Menu Triggers
BMad offers two ways to start work, and they serve different purposes. BMad offers two ways to start work, and they serve different purposes.
| Mechanism | How you invoke it | What happens | | Mechanism | How you invoke it | What happens |
| --- | --- | --- | | --- | --- | --- |
| **Slash command** | Type `/bmad-...` in your IDE | Directly loads an agent, runs a workflow, or executes a task | | **Skill** | Type the skill name (e.g. `bmad-help`) in your IDE | Directly loads an agent, runs a workflow, or executes a task |
| **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character | | **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character |
Agent menu triggers require an active agent session. Use slash commands when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation. Agent menu triggers require an active agent session. Use skills when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation.
## How Commands Are Generated ## How Skills Are Generated
When you run `npx bmad-method install`, the installer reads the manifests for every selected module and writes one command file per agent, workflow, task, and tool. Each file is a short markdown prompt that instructs the AI to load the corresponding source file and follow its instructions. When you run `npx bmad-method install`, the installer reads the manifests for every selected module and writes one skill per agent, workflow, task, and tool. Each skill is a directory containing a `SKILL.md` file that instructs the AI to load the corresponding source file and follow its instructions.
The installer uses templates for each command type: The installer uses templates for each skill type:
| Command type | What the generated file does | | Skill type | What the generated file does |
| --- | --- | | --- | --- |
| **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character | | **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character |
| **Workflow command** | Loads the workflow engine (`workflow.xml`) and passes the workflow config | | **Workflow skill** | Loads the workflow engine (`workflow.xml`) and passes the workflow config |
| **Task command** | Loads a standalone task file and follows its instructions | | **Task skill** | Loads a standalone task file and follows its instructions |
| **Tool command** | Loads a standalone tool file and follows its instructions | | **Tool skill** | Loads a standalone tool file and follows its instructions |
:::note[Re-running the installer] :::note[Re-running the installer]
If you add or remove modules, run the installer again. It regenerates all command files to match your current module selection. If you add or remove modules, run the installer again. It regenerates all skill files to match your current module selection.
::: :::
## Where Command Files Live ## Where Skill Files Live
The installer writes command files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation. The installer writes skill files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation.
| IDE / CLI | Command directory | | IDE / CLI | Skills directory |
| --- | --- | | --- | --- |
| Claude Code | `.claude/commands/` | | Claude Code | `.claude/skills/` |
| Cursor | `.cursor/commands/` | | Cursor | `.cursor/skills/` |
| Windsurf | `.windsurf/workflows/` | | Windsurf | `.windsurf/skills/` |
| Other IDEs | See the installer output for the target path | | Other IDEs | See the installer output for the target path |
All IDEs receive a flat set of command files in their command directory. For example, a Claude Code installation looks like: Each skill is a directory containing a `SKILL.md` file. For example, a Claude Code installation looks like:
```text ```text
.claude/commands/ .claude/skills/
├── bmad-agent-bmm-dev.md ├── bmad-help/
├── bmad-agent-bmm-pm.md │ └── SKILL.md
├── bmad-bmm-create-prd.md ├── bmad-create-prd/
├── bmad-editorial-review-prose.md │ └── SKILL.md
├── bmad-help.md ├── bmad-dev/
│ └── SKILL.md
└── ... └── ...
``` ```
The filename determines the slash command name in your IDE. For example, the file `bmad-agent-bmm-dev.md` registers the command `/bmad-agent-bmm-dev`. The directory name determines the skill name in your IDE. For example, the directory `bmad-dev/` registers the skill `bmad-dev`.
## How to Discover Your Commands ## How to Discover Your Skills
Type `/bmad` in your IDE and use autocomplete to browse available commands. Type the skill name in your IDE to invoke it. Some platforms require you to enable skills in settings before they appear.
Run `/bmad-help` for context-aware guidance on your next step. Run `bmad-help` for context-aware guidance on your next step.
:::tip[Quick discovery] :::tip[Quick discovery]
The generated command folders in your project are the canonical list. Open them in your file explorer to see every command with its description. The generated skill directories in your project are the canonical list. Open them in your file explorer to see every skill with its description.
::: :::
## Command Categories ## Skill Categories
### Agent Commands ### Agent Skills
Agent commands load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers. Agent skills load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers.
| Example command | Agent | Role | | Example skill | Agent | Role |
| --- | --- | --- | | --- | --- | --- |
| `/bmad-agent-bmm-dev` | Amelia (Developer) | Implements stories with strict adherence to specs | | `bmad-dev` | Amelia (Developer) | Implements stories with strict adherence to specs |
| `/bmad-agent-bmm-pm` | John (Product Manager) | Creates and validates PRDs | | `bmad-pm` | John (Product Manager) | Creates and validates PRDs |
| `/bmad-agent-bmm-architect` | Winston (Architect) | Designs system architecture | | `bmad-architect` | Winston (Architect) | Designs system architecture |
| `/bmad-agent-bmm-sm` | Bob (Scrum Master) | Manages sprints and stories | | `bmad-sm` | Bob (Scrum Master) | Manages sprints and stories |
See [Agents](./agents.md) for the full list of default agents and their triggers. See [Agents](./agents.md) for the full list of default agents and their triggers.
### Workflow Commands ### Workflow Skills
Workflow commands run a structured, multi-step process without loading an agent persona first. They load the workflow engine and pass a specific workflow configuration. Workflow skills run a structured, multi-step process without loading an agent persona first. They load the workflow engine and pass a specific workflow configuration.
| Example command | Purpose | | Example skill | Purpose |
| --- | --- | | --- | --- |
| `/bmad-bmm-create-prd` | Create a Product Requirements Document | | `bmad-create-prd` | Create a Product Requirements Document |
| `/bmad-bmm-create-architecture` | Design system architecture | | `bmad-create-architecture` | Design system architecture |
| `/bmad-bmm-dev-story` | Implement a story | | `bmad-create-epics-and-stories` | Create epics and stories |
| `/bmad-bmm-code-review` | Run a code review | | `bmad-dev-story` | Implement a story |
| `/bmad-bmm-quick-spec` | Define an ad-hoc change (Quick Flow) | | `bmad-code-review` | Run a code review |
| `bmad-quick-spec` | Define an ad-hoc change (Quick Flow) |
See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase. See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase.
### Task and Tool Commands ### Task and Tool Skills
Tasks and tools are standalone operations that do not require an agent or workflow context. Tasks and tools are standalone operations that do not require an agent or workflow context.
#### BMad-Help: Your Intelligent Guide #### BMad-Help: Your Intelligent Guide
**`/bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that: **`bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that:
- **Inspects your project** to see what's already been done - **Inspects your project** to see what's already been done
- **Understands natural language queries** — ask questions in plain English - **Understands natural language queries** — ask questions in plain English
@ -116,36 +118,28 @@ Tasks and tools are standalone operations that do not require an agent or workfl
**Examples:** **Examples:**
``` ```
/bmad-help bmad-help
/bmad-help I have a SaaS idea and know all the features. Where do I start? bmad-help I have a SaaS idea and know all the features. Where do I start?
/bmad-help What are my options for UX design? bmad-help What are my options for UX design?
/bmad-help I'm stuck on the PRD workflow bmad-help I'm stuck on the PRD workflow
``` ```
#### Other Tasks and Tools #### Other Tasks and Tools
| Example command | Purpose | | Example skill | Purpose |
| --- | --- | | --- | --- |
| `/bmad-shard-doc` | Split a large markdown file into smaller sections | | `bmad-shard-doc` | Split a large markdown file into smaller sections |
| `/bmad-index-docs` | Index project documentation | | `bmad-index-docs` | Index project documentation |
| `/bmad-editorial-review-prose` | Review document prose quality | | `bmad-editorial-review-prose` | Review document prose quality |
## Naming Convention ## Naming Convention
Command names follow a predictable pattern. All skills use the `bmad-` prefix followed by a descriptive name (e.g., `bmad-dev`, `bmad-create-prd`, `bmad-help`). See [Modules](./modules.md) for available modules.
| Pattern | Meaning | Example |
| --- | --- | --- |
| `bmad-agent-<module>-<name>` | Agent launcher | `bmad-agent-bmm-dev` |
| `bmad-<module>-<workflow>` | Workflow command | `bmad-bmm-create-prd` |
| `bmad-<name>` | Core task or tool | `bmad-help` |
Module codes: `bmm` (Agile suite), `bmb` (Builder), `tea` (Test Architect), `cis` (Creative Intelligence), `gds` (Game Dev Studio). See [Modules](./modules.md) for descriptions.
## Troubleshooting ## Troubleshooting
**Commands not appearing after install.** Restart your IDE or reload the window. Some IDEs cache the command list and require a refresh to pick up new files. **Skills not appearing after install.** Some platforms require skills to be explicitly enabled in settings. Check your IDE's documentation or ask your AI assistant how to enable skills. You may also need to restart your IDE or reload the window.
**Expected commands are missing.** The installer only generates commands for modules you selected. Run `npx bmad-method install` again and verify your module selection. Check that the command files exist in the expected directory. **Expected skills are missing.** The installer only generates skills for modules you selected. Run `npx bmad-method install` again and verify your module selection. Check that the skill files exist in the expected directory.
**Commands from a removed module still appear.** The installer does not delete old command files automatically. Remove the stale files from your IDE's command directory, or delete the entire command directory and re-run the installer for a clean set. **Skills from a removed module still appear.** The installer does not delete old skill files automatically. Remove the stale directories from your IDE's skills directory, or delete the entire skills directory and re-run the installer for a clean set.

2
docs/reference/testing.md
View File

@ -26,7 +26,7 @@ Most projects should start with Quinn. If you later need test strategy, quality
Quinn is the built-in QA agent in the BMM (Agile suite) module. It generates working tests quickly using your project's existing test framework -- no configuration or additional installation required. Quinn is the built-in QA agent in the BMM (Agile suite) module. It generates working tests quickly using your project's existing test framework -- no configuration or additional installation required.
**Trigger:** `QA` or `bmad-bmm-qa-automate` **Trigger:** `QA` or `bmad-qa-generate-e2e-tests`
### What Quinn Does ### What Quinn Does

38
docs/reference/workflow-map.md
View File

@ -9,9 +9,9 @@ The BMad Method (BMM) is a module in the BMad Ecosystem, targeted at following t
The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework. The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework.
If at any time you are unsure what to do, the `/bmad-help` command will help you stay on track or know what to do next. You can always refer to this for reference also - but /bmad-help is fully interactive and much quicker if you have already installed the BMad Method. Additionally, if you are using different modules that have extended the BMad Method or added other complementary non-extension modules - the /bmad-help evolves to know all that is available to give you the best in-the-moment advice. If at any time you are unsure what to do, the `bmad-help` skill will help you stay on track or know what to do next. You can always refer to this for reference also - but `bmad-help` is fully interactive and much quicker if you have already installed the BMad Method. Additionally, if you are using different modules that have extended the BMad Method or added other complementary non-extension modules - `bmad-help` evolves to know all that is available to give you the best in-the-moment advice.
Final important note: Every workflow below can be run directly with your tool of choice via slash command or by loading an agent first and using the entry from the agents menu. Final important note: Every workflow below can be run directly with your tool of choice via skill or by loading an agent first and using the entry from the agents menu.
<iframe src="/workflow-map-diagram.html" title="BMad Method Workflow Map Diagram" width="100%" height="100%" style="border-radius: 8px; border: 1px solid #334155; min-height: 900px;"></iframe> <iframe src="/workflow-map-diagram.html" title="BMad Method Workflow Map Diagram" width="100%" height="100%" style="border-radius: 8px; border: 1px solid #334155; min-height: 900px;"></iframe>
@ -26,8 +26,8 @@ Explore the problem space and validate ideas before committing to planning.
| Workflow | Purpose | Produces | | Workflow | Purpose | Produces |
| ------------------------------- | -------------------------------------------------------------------------- | ------------------------- | | ------------------------------- | -------------------------------------------------------------------------- | ------------------------- |
| `bmad-brainstorming` | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` | | `bmad-brainstorming` | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` |
| `bmad-bmm-research` | Validate market, technical, or domain assumptions | Research findings | | `bmad-domain-research`, `bmad-market-research`, `bmad-technical-research` | Validate market, technical, or domain assumptions | Research findings |
| `bmad-bmm-create-product-brief` | Capture strategic vision | `product-brief.md` | | `bmad-create-product-brief` | Capture strategic vision | `product-brief.md` |
## Phase 2: Planning ## Phase 2: Planning
@ -35,8 +35,8 @@ Define what to build and for whom.
| Workflow | Purpose | Produces | | Workflow | Purpose | Produces |
| --------------------------- | ---------------------------------------- | ------------ | | --------------------------- | ---------------------------------------- | ------------ |
| `bmad-bmm-create-prd` | Define requirements (FRs/NFRs) | `PRD.md` | | `bmad-create-prd` | Define requirements (FRs/NFRs) | `PRD.md` |
| `bmad-bmm-create-ux-design` | Design user experience (when UX matters) | `ux-spec.md` | | `bmad-create-ux-design` | Design user experience (when UX matters) | `ux-spec.md` |
## Phase 3: Solutioning ## Phase 3: Solutioning
@ -44,9 +44,9 @@ Decide how to build it and break work into stories.
| Workflow | Purpose | Produces | | Workflow | Purpose | Produces |
| ----------------------------------------- | ------------------------------------------ | --------------------------- | | ----------------------------------------- | ------------------------------------------ | --------------------------- |
| `bmad-bmm-create-architecture` | Make technical decisions explicit | `architecture.md` with ADRs | | `bmad-create-architecture` | Make technical decisions explicit | `architecture.md` with ADRs |
| `bmad-bmm-create-epics-and-stories` | Break requirements into implementable work | Epic files with stories | | `bmad-create-epics-and-stories` | Break requirements into implementable work | Epic files with stories |
| `bmad-bmm-check-implementation-readiness` | Gate check before implementation | PASS/CONCERNS/FAIL decision | | `bmad-check-implementation-readiness` | Gate check before implementation | PASS/CONCERNS/FAIL decision |
## Phase 4: Implementation ## Phase 4: Implementation
@ -54,13 +54,13 @@ Build it, one story at a time. Coming soon, full phase 4 automation!
| Workflow | Purpose | Produces | | Workflow | Purpose | Produces |
| -------------------------- | ------------------------------------------------------------------------ | -------------------------------- | | -------------------------- | ------------------------------------------------------------------------ | -------------------------------- |
| `bmad-bmm-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle) | `sprint-status.yaml` | | `bmad-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle) | `sprint-status.yaml` |
| `bmad-bmm-create-story` | Prepare next story for implementation | `story-[slug].md` | | `bmad-create-story` | Prepare next story for implementation | `story-[slug].md` |
| `bmad-bmm-dev-story` | Implement the story | Working code + tests | | `bmad-dev-story` | Implement the story | Working code + tests |
| `bmad-bmm-code-review` | Validate implementation quality | Approved or changes requested | | `bmad-code-review` | Validate implementation quality | Approved or changes requested |
| `bmad-bmm-correct-course` | Handle significant mid-sprint changes | Updated plan or re-routing | | `bmad-correct-course` | Handle significant mid-sprint changes | Updated plan or re-routing |
| `bmad-bmm-automate` | Generate tests for existing features - Use after a full epic is complete | End to End UI Focused Test suite | | `bmad-sprint-status` | Track sprint progress and story status | Sprint status update |
| `bmad-bmm-retrospective` | Review after epic completion | Lessons learned | | `bmad-retrospective` | Review after epic completion | Lessons learned |
## Quick Flow (Parallel Track) ## Quick Flow (Parallel Track)
@ -68,8 +68,8 @@ Skip phases 1-3 for small, well-understood work.
| Workflow | Purpose | Produces | | Workflow | Purpose | Produces |
| --------------------- | ------------------------------------------ | --------------------------------------------- | | --------------------- | ------------------------------------------ | --------------------------------------------- |
| `bmad-bmm-quick-spec` | Define an ad-hoc change | `tech-spec.md` (story file for small changes) | | `bmad-quick-spec` | Define an ad-hoc change | `tech-spec.md` (story file for small changes) |
| `bmad-bmm-quick-dev` | Implement from spec or direct instructions | Working code + tests | | `bmad-quick-dev` | Implement from spec or direct instructions | Working code + tests |
## Context Management ## Context Management
@ -84,6 +84,6 @@ Create `project-context.md` to ensure AI agents follow your project's rules and
**How to create it:** **How to create it:**
- **Manually** — Create `_bmad-output/project-context.md` with your technology stack and implementation rules - **Manually** — Create `_bmad-output/project-context.md` with your technology stack and implementation rules
- **Generate it** — Run `/bmad-bmm-generate-project-context` to auto-generate from your architecture or codebase - **Generate it** — Run `bmad-generate-project-context` to auto-generate from your architecture or codebase
[**Learn more about project-context.md**](../explanation/project-context.md) [**Learn more about project-context.md**](../explanation/project-context.md)

68
docs/tutorials/getting-started.md
View File

@ -37,16 +37,16 @@ Build software faster using AI-powered workflows with specialized agents that gu
### How to Use BMad-Help ### How to Use BMad-Help
Run it in your AI IDE with just the slash command: Run it in your AI IDE by invoking the skill:
``` ```
/bmad-help bmad-help
``` ```
Or combine it with a question for context-aware guidance: Or combine it with a question for context-aware guidance:
``` ```
/bmad-help I have an idea for a SaaS product, I already know all the features I want. where do I get started? bmad-help I have an idea for a SaaS product, I already know all the features I want. where do I get started?
``` ```
BMad-Help will respond with: BMad-Help will respond with:
@ -112,7 +112,7 @@ BMad-Help will detect what you've completed and recommend exactly what to do nex
::: :::
:::note[How to Load Agents and Run Workflows] :::note[How to Load Agents and Run Workflows]
Each workflow has a **slash command** you run in your IDE (e.g., `/bmad-bmm-create-prd`). Running a workflow command automatically loads the appropriate agent — you don't need to load agents separately. You can also load an agent directly for general conversation (e.g., `/bmad-agent-bmm-pm` for the PM agent). Each workflow has a **skill** you invoke in your IDE (e.g., `/bmad-create-prd`). Running a workflow skill automatically loads the appropriate agent — you don't need to load agents separately. You can also invoke an agent directly for general conversation (e.g., `/bmad-pm` for the PM agent).
::: :::
:::caution[Fresh Chats] :::caution[Fresh Chats]
@ -126,35 +126,35 @@ Work through phases 1-3. **Use fresh chats for each workflow.**
:::tip[Project Context (Optional)] :::tip[Project Context (Optional)]
Before starting, consider creating `project-context.md` to document your technical preferences and implementation rules. This ensures all AI agents follow your conventions throughout the project. Before starting, consider creating `project-context.md` to document your technical preferences and implementation rules. This ensures all AI agents follow your conventions throughout the project.
Create it manually at `_bmad-output/project-context.md` or generate it after architecture using `/bmad-bmm-generate-project-context`. [Learn more](../explanation/project-context.md). Create it manually at `_bmad-output/project-context.md` or generate it after architecture using `/bmad-generate-project-context`. [Learn more](../explanation/project-context.md).
::: :::
### Phase 1: Analysis (Optional) ### Phase 1: Analysis (Optional)
All workflows in this phase are optional: All workflows in this phase are optional:
- **brainstorming** (`/bmad-brainstorming`) — Guided ideation - **brainstorming** (`/bmad-brainstorming`) — Guided ideation
- **research** (`/bmad-bmm-research`) — Market and technical research - **research** (`/bmad-research`) — Market and technical research
- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document - **create-product-brief** (`/bmad-create-product-brief`) — Recommended foundation document
### Phase 2: Planning (Required) ### Phase 2: Planning (Required)
**For BMad Method and Enterprise tracks:** **For BMad Method and Enterprise tracks:**
1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat 1. Invoke the **PM agent** (`/bmad-pm`) in a new chat
2. Run the `prd` workflow (`/bmad-bmm-create-prd`) 2. Run the `bmad-create-prd` workflow (`/bmad-create-prd`)
3. Output: `PRD.md` 3. Output: `PRD.md`
**For Quick Flow track:** **For Quick Flow track:**
- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation - Use the `bmad-quick-spec` workflow (`/bmad-quick-spec`) instead of PRD, then skip to implementation
:::note[UX Design (Optional)] :::note[UX Design (Optional)]
If your project has a user interface, load the **UX-Designer agent** (`/bmad-agent-bmm-ux-designer`) and run the UX design workflow (`/bmad-bmm-create-ux-design`) after creating your PRD. If your project has a user interface, invoke the **UX-Designer agent** (`/bmad-ux-designer`) and run the UX design workflow (`/bmad-create-ux-design`) after creating your PRD.
::: :::
### Phase 3: Solutioning (BMad Method/Enterprise) ### Phase 3: Solutioning (BMad Method/Enterprise)
**Create Architecture** **Create Architecture**
1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat 1. Invoke the **Architect agent** (`/bmad-architect`) in a new chat
2. Run `create-architecture` (`/bmad-bmm-create-architecture`) 2. Run `bmad-create-architecture` (`/bmad-create-architecture`)
3. Output: Architecture document with technical decisions 3. Output: Architecture document with technical decisions
**Create Epics and Stories** **Create Epics and Stories**
@ -163,13 +163,13 @@ If your project has a user interface, load the **UX-Designer agent** (`/bmad-age
Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down. Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down.
::: :::
1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat 1. Invoke the **PM agent** (`/bmad-pm`) in a new chat
2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`) 2. Run `bmad-create-epics-and-stories` (`/bmad-create-epics-and-stories`)
3. The workflow uses both PRD and Architecture to create technically-informed stories 3. The workflow uses both PRD and Architecture to create technically-informed stories
**Implementation Readiness Check** *(Highly Recommended)* **Implementation Readiness Check** *(Highly Recommended)*
1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat 1. Invoke the **Architect agent** (`/bmad-architect`) in a new chat
2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`) 2. Run `bmad-check-implementation-readiness` (`/bmad-check-implementation-readiness`)
3. Validates cohesion across all planning documents 3. Validates cohesion across all planning documents
## Step 2: Build Your Project ## Step 2: Build Your Project
@ -178,7 +178,7 @@ Once planning is complete, move to implementation. **Each workflow should run in
### Initialize Sprint Planning ### Initialize Sprint Planning
Load the **SM agent** (`/bmad-agent-bmm-sm`) and run `sprint-planning` (`/bmad-bmm-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories. Invoke the **SM agent** (`/bmad-sm`) and run `bmad-sprint-planning` (`/bmad-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
### The Build Cycle ### The Build Cycle
@ -186,11 +186,11 @@ For each story, repeat this cycle with fresh chats:
| Step | Agent | Workflow | Command | Purpose | | Step | Agent | Workflow | Command | Purpose |
| ---- | ----- | -------------- | -------------------------- | ---------------------------------- | | ---- | ----- | -------------- | -------------------------- | ---------------------------------- |
| 1 | SM | `create-story` | `/bmad-bmm-create-story` | Create story file from epic | | 1 | SM | `bmad-create-story` | `/bmad-create-story` | Create story file from epic |
| 2 | DEV | `dev-story` | `/bmad-bmm-dev-story` | Implement the story | | 2 | DEV | `bmad-dev-story` | `/bmad-dev-story` | Implement the story |
| 3 | DEV | `code-review` | `/bmad-bmm-code-review` | Quality validation *(recommended)* | | 3 | DEV | `bmad-code-review` | `/bmad-code-review` | Quality validation *(recommended)* |
After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`). After completing all stories in an epic, invoke the **SM agent** (`/bmad-sm`) and run `bmad-retrospective` (`/bmad-retrospective`).
## What You've Accomplished ## What You've Accomplished
@ -221,16 +221,16 @@ your-project/
| Workflow | Command | Agent | Purpose | | Workflow | Command | Agent | Purpose |
| ------------------------------------- | ------------------------------------------ | --------- | ----------------------------------------------- | | ------------------------------------- | ------------------------------------------ | --------- | ----------------------------------------------- |
| **`help`** ⭐ | `/bmad-help` | Any | **Your intelligent guide — ask anything!** | | **`bmad-help`** ⭐ | `/bmad-help` | Any | **Your intelligent guide — ask anything!** |
| `prd` | `/bmad-bmm-create-prd` | PM | Create Product Requirements Document | | `bmad-create-prd` | `/bmad-create-prd` | PM | Create Product Requirements Document |
| `create-architecture` | `/bmad-bmm-create-architecture` | Architect | Create architecture document | | `bmad-create-architecture` | `/bmad-create-architecture` | Architect | Create architecture document |
| `generate-project-context` | `/bmad-bmm-generate-project-context` | Analyst | Create project context file | | `bmad-generate-project-context` | `/bmad-generate-project-context` | Analyst | Create project context file |
| `create-epics-and-stories` | `/bmad-bmm-create-epics-and-stories` | PM | Break down PRD into epics | | `bmad-create-epics-and-stories` | `/bmad-create-epics-and-stories` | PM | Break down PRD into epics |
| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion | | `bmad-check-implementation-readiness` | `/bmad-check-implementation-readiness` | Architect | Validate planning cohesion |
| `sprint-planning` | `/bmad-bmm-sprint-planning` | SM | Initialize sprint tracking | | `bmad-sprint-planning` | `/bmad-sprint-planning` | SM | Initialize sprint tracking |
| `create-story` | `/bmad-bmm-create-story` | SM | Create a story file | | `bmad-create-story` | `/bmad-create-story` | SM | Create a story file |
| `dev-story` | `/bmad-bmm-dev-story` | DEV | Implement a story | | `bmad-dev-story` | `/bmad-dev-story` | DEV | Implement a story |
| `code-review` | `/bmad-bmm-code-review` | DEV | Review implemented code | | `bmad-code-review` | `/bmad-code-review` | DEV | Review implemented code |
## Common Questions ## Common Questions
@ -238,10 +238,10 @@ your-project/
Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation. Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation.
**Can I change my plan later?** **Can I change my plan later?**
Yes. The SM agent has a `correct-course` workflow (`/bmad-bmm-correct-course`) for handling scope changes. Yes. The SM agent has a `bmad-correct-course` workflow (`/bmad-correct-course`) for handling scope changes.
**What if I want to brainstorm first?** **What if I want to brainstorm first?**
Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD. Invoke the Analyst agent (`/bmad-analyst`) and run `bmad-brainstorming` (`/bmad-brainstorming`) before starting your PRD.
**Do I need to follow a strict order?** **Do I need to follow a strict order?**
Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above. Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above.