BMAD-METHOD/docs/reference/agents.md at cfee292715a09e7a24318e0edac8460595509cbf

mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-08-30 17:14:59 +08:00

Files

T

Alex Verkhovsky 7b2d90a5f0 chore(bmm): retire bmad-investigate skill and its documentation (#2509 )

* chore(bmm): retire bmad-investigate skill and its documentation

Removes the bmad-investigate skill, its case-file template, the EN/FR
forensic-investigation explainer docs, and every integration point:
Amelia's `IN` menu entry, the plugin marketplace manifest, module-help,
the workflow-map tables and HTML diagrams, and the agent-trigger tables.
EN/FR explanation sidebar orders are renumbered to close the gap left by
the removed doc.

Rationale: the skill's only non-redundant value was a durable, hand-off
case-file artifact — a workflow that is unproven in practice. Everything
else (evidence grading, hypothesis discipline, causal tracing) is
behavior a capable model already performs without a dedicated skill. The
skill also carried method-internal metaphor ("stronghold", "evidence
perimeter") that leaked into user-facing chat. Upstream signals agreed:
issue #2452 flagged the vocabulary leak and a maintainer noted the skill
should not auto-fire. Added in #2364.

Supersedes the in-flight cleanup in #2478 and resolves #2452 by removal.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore(bmm): add bmad-investigate to removals.txt and note retirement

The retirement commit removed the skill source and docs but did not add
the removals.txt entry that triggers cleanup of the skill directory on
existing installs during update. Add it, plus an Unreleased CHANGELOG note.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-24 19:42:10 -07:00

3.4 KiB

Raw Blame History

title, description, sidebar

title

description

sidebar

Agents

Default BMM agents with their skill IDs, menu triggers, and primary workflows

order
2

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-agent-dev) is used to invoke the agent.
Triggers are the short menu codes (e.g., PRD) and fuzzy matches shown in each agent menu.
QA test generation is handled by the bmad-qa-generate-e2e-tests workflow skill, available through the Developer agent. The full Test Architect (TEA) lives in its own module.

Agent	Skill ID	Triggers	Primary workflows
Analyst (Mary)	`bmad-agent-analyst`	`BP`, `MR`, `DR`, `TR`, `CB`, `WB`, `DP`	Brainstorm, Market Research, Domain Research, Technical Research, Create Brief, PRFAQ Challenge, Document Project
Product Manager (John)	`bmad-agent-pm`	`PRD`, `CE`, `IR`, `CC`	Create/Update/Validate PRD, Create Epics and Stories, Implementation Readiness, Correct Course
Architect (Winston)	`bmad-agent-architect`	`CA`, `IR`	Create Architecture, Implementation Readiness
Developer (Amelia)	`bmad-agent-dev`	`DS`, `QD`, `QA`, `CR`, `SP`, `CS`, `ER`	Dev Story, Quick Dev, QA Test Generation, Code Review, Sprint Planning, Create Story, Epic Retrospective
UX Designer (Sally)	`bmad-agent-ux-designer`	`CU`	Create UX Design
Technical Writer (Paige)	`bmad-agent-tech-writer`	`DP`, `WD`, `MG`, `VD`, `EC`	Document Project, Write Document, 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: PRD (Create, update, or validate 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)	`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

3.4 KiB Raw Blame History