Files
BMAD-METHOD/docs/explanation/core-concepts/agent-roles.md
forcetrainer 12d3492e0c Add link auditor, reorganize documentation, and README update (#1277)
* feat: add link auditor tools and fix broken docs links

- Add audit-doc-links.js to scan docs for broken links with auto-resolution
- Add fix-doc-links.js to apply suggested fixes (dry-run by default)
- Remove stale "Back to Core Concepts" breadcrumb links
- Update BMad acronym to "Breakthrough Method of Agile AI Driven Development"
- Update README links to docs.bmad-method.org
- Simplify upgrade callout in getting-started tutorial

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: reorganize docs structure and archive v4 tutorial

- Remove unused section index files (tutorials, how-to, explanation, reference)
- Move getting-started-bmadv4.md to _archive
- Update quick-start-bmgd.md to remove archived file reference
- Update upgrade-to-v6.md
- Update astro.config.mjs for new structure

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: ignore underscore directories in link checker

Update check-doc-links.js to skip _archive, _planning, and other
underscore-prefixed directories when validating links.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: add v4 users section to README

Add links to v4 documentation archive and upgrade guide for users
migrating from previous versions.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat: convert docs to site-relative links and add validation tools

- Convert all relative links (./  ../) to site-relative paths (/path/)
- Strip .md extensions and use trailing slashes for Astro/Starlight
- Add fix-doc-links.js to convert relative links to site-relative
- Add validate-doc-links.js to check links point to existing files
- Remove old audit-doc-links.js and check-doc-links.js
- Update build-docs.js to use new validation script
- Add npm scripts: docs:fix-links, docs:validate-links
- Update style guide with validation steps

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: standardize acronym to BMad across documentation

Replace incorrect "BMAD" with correct "BMad" in text and frontmatter
while preserving "BMAD-METHOD" in GitHub URLs.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: fix BMad acronym and remove draft README

- Correct acronym to "Breakthrough Method of Agile AI Driven Development"
- Remove unused README-draft.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: standardize BMad acronym in README

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: standardize FAQ format across all FAQ pages

- Add TOC with jump links under "## Questions"
- Use ### headers for questions (no Q: prefix)
- Direct answers without **A:** prefix
- Remove horizontal rules and "Related Documentation" sections
- End each FAQ with issue/Discord CTA
- Update style guide with new FAQ guidelines
- Delete redundant faq/index.md (sidebar handles navigation)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: use repo-relative links with .md for GitHub compatibility

Convert all documentation links to repo-relative format (/docs/path/file.md)
so they work when browsing on GitHub. The rehype plugin strips /docs/ prefix
and converts .md to trailing slash at build time for Astro/Starlight.

- Update rehype-markdown-links.js to strip /docs/ prefix from absolute paths
- Update fix-doc-links.js to generate /docs/ prefixed paths with .md extension
- Convert 217 links across 64 files to new format

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: handle /docs/ prefix in link validator

Update resolveLink to strip /docs/ prefix from repo-relative links
before checking if files exist.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: restore FAQ index page

Re-add the FAQ index page that was accidentally deleted, with
updated repo-relative link format.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
2026-01-10 02:55:33 +08:00

4.6 KiB

title, description
title description
Agent Roles in BMad Method Understanding the different 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.


Core Agents Overview

Agent Role Primary Phase
Analyst Research and discovery Phase 1 (Analysis)
PM Requirements and planning Phase 2 (Planning)
Architect Technical design Phase 3 (Solutioning)
SM Sprint orchestration Phase 4 (Implementation)
DEV Code implementation Phase 4 (Implementation)
TEA Test architecture Phases 3-4 (Cross-phase)
UX Designer User experience Phase 2-3
Quick Flow Solo Dev Fast solo development All phases (Quick Flow)

Phase 1: Analysis

Analyst (Mary)

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.


Phase 2: Planning

PM (John)

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.

UX Designer (Sally)

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.


Phase 3: Solutioning

Architect (Winston)

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.


Phase 4: Implementation

SM (Bob)

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.

DEV (Amelia)

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.


Cross-Phase Agents

TEA (Murat)

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.


Quick Flow

Quick Flow Solo Dev (Barry)

Fast solo development without handoffs.

Responsibilities:

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

Key Workflows:

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

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


Choosing the Right Agent

Task Agent
Brainstorming ideas Analyst
Market research Analyst
Creating PRD PM
Designing UX UX Designer
System architecture Architect
Preparing stories SM
Writing code DEV
Setting up tests TEA
Quick bug fix Quick Flow Solo Dev