Agents¶
BMAtlassian uses 9 AI agent personas, each with a distinct role, communication style, and set of workflows. When a slash command is invoked, Claude adopts the specified agent persona and follows its workflow instructions.
Agent Roster¶
| Agent | Persona | Role | Phase |
|---|---|---|---|
| Analyst | Mary | Creates product briefs, brainstorms, conducts research | 1 - Analysis |
| PM | John | Creates/validates/edits PRDs, defines epics and stories | 2 - Planning |
| UX Designer | Sally | Creates UX design specifications | 2 - Planning |
| Architect | Winston | Defines architecture and technology decisions | 3 - Solutioning |
| SM (Scrum Master) | Bob | Manages sprints, prepares stories, runs retros | 3-4 - Solutioning/Implementation |
| Dev | Amelia | Implements stories, writes code, creates branches and PRs | 4 - Implementation |
| QA | Quinn | Reviews code, generates tests, validates ACs, reviews PRs | 4 - Implementation |
| Quick Flow | Barry | One-off specs and implementation without full planning | Anytime |
| Tech Writer | Paige | Documents projects, reviews prose and structure | Anytime |
How Agents Communicate¶
Agents communicate through Jira, not shared files:
- Handoff labels -- when an agent completes work, it applies a
bmad-handoff-{agent}label to signal the next agent - Jira comments -- agents post structured records (dev records, review findings, test summaries) as comments
- Agent locking -- the
agent-activelabel prevents concurrent work on the same issue - Structured context -- handoff comments carry decisions, open questions, and artefact references
The orchestrator uses these signals to automatically dispatch the correct agent.
Review & Editorial Tools¶
These workflows are not tied to a specific agent persona — they can be invoked standalone or from within any agent context:
| Command | Description |
|---|---|
/bmad-atlassian-adversarial-review |
Cynical adversarial review of any Confluence document |
/bmad-atlassian-editorial-prose |
Review prose clarity and tone on Confluence |
/bmad-atlassian-editorial-structure |
Review document organization on Confluence |
/bmad-atlassian-edge-case-hunter |
Find unhandled edge cases, post findings to Jira |
/bmad-atlassian-party-mode |
Multi-agent discussion on any topic |
/bmad-atlassian-project-dashboard |
Project status dashboard on Confluence |
System Mechanisms¶
The Orchestrator (/bmad-atlassian-orchestrate) is not an agent persona — it is a system dispatch mechanism that polls Jira state and routes work to the correct agent automatically. See the Orchestrator Guide.
Agent Definitions¶
Agent definitions live in _bmad/atlassian/agents/*.agent.yaml. Each file specifies the agent's persona, critical actions, and available workflows.