54 lines
3.1 KiB
Markdown
54 lines
3.1 KiB
Markdown
---
|
|
title: Agents
|
|
description: Default BMM agents with their skill IDs, menu triggers, and primary workflows (Analyst, Architect, UX Designer, Technical Writer)
|
|
sidebar:
|
|
order: 2
|
|
---
|
|
|
|
## Default Agents
|
|
|
|
This page lists the four 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
|
|
|
|
- Each agent is available as a skill, generated by the installer. The skill ID (e.g., `bmad-analyst`) is used to invoke the agent.
|
|
- Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu.
|
|
- QA test generation is handled by the `bmad-qa-generate-e2e-tests` workflow skill. The full Test Architect (TEA) lives in its own module.
|
|
|
|
| Agent | Skill ID | Triggers | Primary workflows |
|
|
| ---------------------- | ------------------ | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
|
|
| Analyst (Mary) | `bmad-analyst` | `BP`, `RS`, `CB`, `DP` | Brainstorm Project, Research, Create Brief, Document Project |
|
|
| Architect (Winston) | `bmad-architect` | `CA`, `IR` | Create Architecture, Implementation Readiness |
|
|
| UX Designer (Sally) | `bmad-ux-designer` | `CU` | Create UX Design |
|
|
| Technical Writer (Paige) | `bmad-tech-writer` | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |
|
|
|
|
## Trigger Types
|
|
|
|
Agent menu triggers use two different invocation types. Knowing which type a trigger uses helps you provide the right input.
|
|
|
|
### Workflow triggers (no arguments needed)
|
|
|
|
Most triggers load a structured workflow file. Type the trigger code and the agent starts the workflow, prompting you for input at each step.
|
|
|
|
Examples: `CP` (Create PRD), `DS` (Dev Story), `CA` (Create Architecture), `QS` (Quick Spec)
|
|
|
|
### Conversational triggers (arguments required)
|
|
|
|
Some triggers start a free-form conversation instead of a structured workflow. These expect you to describe what you need alongside the trigger code.
|
|
|
|
| Agent | Trigger | What to provide |
|
|
| --- | --- | --- |
|
|
| Technical Writer (Paige) | `WD` | Description of the document to write |
|
|
| Technical Writer (Paige) | `US` | Preferences or conventions to add to standards |
|
|
| Technical Writer (Paige) | `MG` | Diagram description and type (sequence, flowchart, etc.) |
|
|
| Technical Writer (Paige) | `VD` | Document to validate and focus areas |
|
|
| Technical Writer (Paige) | `EC` | Concept name to explain |
|
|
|
|
**Example:**
|
|
|
|
```text
|
|
WD Write a deployment guide for our Docker setup
|
|
MG Create a sequence diagram showing the auth flow
|
|
EC Explain how the module system works
|
|
```
|