Skip to content
🤖 Consolidated, AI-optimized BMAD docs: llms-full.txt. Fetch this plain text file for complete context.

Agent Roles in BMad Method

BMad Method uses specialized AI agents, each with a distinct role, expertise, and personality. Understanding these roles helps you know which agent to use for each task.


AgentRolePrimary Phase
AnalystResearch and discoveryPhase 1 (Analysis)
PMRequirements and planningPhase 2 (Planning)
ArchitectTechnical designPhase 3 (Solutioning)
SMSprint orchestrationPhase 4 (Implementation)
DEVCode implementationPhase 4 (Implementation)
TEATest architecturePhases 3-4 (Cross-phase)
UX DesignerUser experiencePhase 2-3
Quick Flow Solo DevFast solo developmentAll phases (Quick Flow)

Business analysis and research specialist.

Responsibilities:

  • Brainstorming and ideation
  • Market, domain, and competitive research
  • Product brief creation
  • Brownfield project documentation

Key Workflows:

  • *brainstorm-project
  • *research
  • *product-brief
  • *document-project

When to use: Starting new projects, exploring ideas, validating market fit, documenting existing codebases.


Product requirements and planning expert.

Responsibilities:

  • Creating Product Requirements Documents
  • Defining functional and non-functional requirements
  • Breaking requirements into epics and stories
  • Validating implementation readiness

Key Workflows:

  • *create-prd
  • *create-epics-and-stories
  • *implementation-readiness

When to use: Defining what to build, creating PRDs, organizing work into stories.

User experience and UI design specialist.

Responsibilities:

  • UX specification creation
  • User journey mapping
  • Wireframe and mockup design
  • Design system documentation

Key Workflows:

  • *create-ux-design
  • *validate-design

When to use: When UX is a primary differentiator, complex user workflows, design system creation.


System architecture and technical design expert.

Responsibilities:

  • System architecture design
  • Architecture Decision Records (ADRs)
  • Technical standards definition
  • Implementation readiness validation

Key Workflows:

  • *create-architecture
  • *implementation-readiness

When to use: Multi-epic projects, cross-cutting technical decisions, preventing agent conflicts.


Sprint planning and story preparation orchestrator.

Responsibilities:

  • Sprint planning and tracking
  • Story preparation for development
  • Course correction handling
  • Epic retrospectives

Key Workflows:

  • *sprint-planning
  • *create-story
  • *correct-course
  • *epic-retrospective

When to use: Organizing work, preparing stories, tracking progress.

Story implementation and code review specialist.

Responsibilities:

  • Story implementation with tests
  • Code review
  • Following architecture patterns
  • Quality assurance

Key Workflows:

  • *dev-story
  • *code-review

When to use: Writing code, implementing stories, reviewing quality.


Test architecture and quality strategy expert.

Responsibilities:

  • Test framework setup
  • Test design and planning
  • ATDD and automation
  • Quality gate decisions

Key Workflows:

  • *framework, *ci
  • *test-design, *atdd, *automate
  • *test-review, *trace, *nfr-assess

When to use: Setting up testing, creating test plans, quality gates.


Fast solo development without handoffs.

Responsibilities:

  • Technical specification
  • End-to-end implementation
  • Code review

Key Workflows:

  • *quick-spec
  • *quick-dev
  • *code-review

When to use: Bug fixes, small features, rapid prototyping.


TaskAgent
Brainstorming ideasAnalyst
Market researchAnalyst
Creating PRDPM
Designing UXUX Designer
System architectureArchitect
Preparing storiesSM
Writing codeDEV
Setting up testsTEA
Quick bug fixQuick Flow Solo Dev