mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-08-29 03:44:18 +08:00
Brian
abfc56bd2c
* feat: add bmad-prfaq skill as alternative to product brief Add Working Backwards PRFAQ challenge skill for stress-testing product concepts through Amazon's PRFAQ methodology. Includes press release drafting, customer FAQ, internal FAQ, and verdict stages with subagent support for artifact scanning and web research. - New bmad-prfaq skill with 5-stage interactive gauntlet and headless mode - Subagents for artifact analysis and web research (graceful degradation) - Research-grounded output directive for current market/competitive data - Always produces distillate for downstream PRD consumption - Fix manifest array syntax in both prfaq and product-brief manifests - Drop number prefixes from reference files - Update docs: getting-started, workflow-map, agents, skills reference - Add analysis-phase explainer doc with comparison table and decision guide - Update workflow-map-diagram.html with prfaq card - Add -H and -A args to CSV for both skills - Add unist-util-visit as devDependency (was imported but undeclared) * fix: harden bmad-prfaq for compaction resilience and context efficiency Add coaching persona re-anchors to all stage prompts so the behavioral directive survives context compaction. Add do-not-read guards at resume detection, headless mode, and input gathering to prevent parent agent context bloat. Add Stage 1 coaching notes capture. Adapt template and press release stage for non-commercial concept types. Cap subagent response token budgets. * fix: add config.user.yaml to file-ref validator allowlist Also update PRFAQ config path to use correct _config/bmm/ prefix.
4.0 KiB
4.0 KiB
title, description, sidebar
| title | description | sidebar | ||
|---|---|---|---|---|
| Agents | Default BMM agents with their skill IDs, menu triggers, and primary workflows |
|
Default Agents
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
- 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. - QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
| Agent | Skill ID | Triggers | Primary workflows |
|---|---|---|---|
| Analyst (Mary) | bmad-analyst |
BP, RS, CB, WB, DP |
Brainstorm Project, Research, Create Brief, PRFAQ Challenge, Document Project |
| 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) | bmad-architect |
CA, IR |
Create Architecture, Implementation Readiness |
| Scrum Master (Bob) | bmad-sm |
SP, CS, ER, CC |
Sprint Planning, Create Story, Epic Retrospective, Correct Course |
| Developer (Amelia) | bmad-dev |
DS, CR |
Dev Story, Code Review |
| QA Engineer (Quinn) | bmad-qa |
QA |
Automate (generate tests for existing features) |
| Quick Flow Solo Dev (Barry) | bmad-master |
QD, CR |
Quick Dev, Code Review |
| 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), QD (Quick Dev)
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:
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