Artefact Mapping¶

The artefact mapping (_bmad/atlassian/artefact-mapping.yaml) is the authoritative reference for how each BMAD artefact maps to Jira or Confluence. Agents consult this file to determine which MCP tool to call for each output.

All output goes exclusively to Jira/Confluence -- no local file writes (with one exception: Project Context also saves a local copy).

Phase 1 -- Analysis¶

Artefact	Destination	MCP Tool	Labels	Key Map Entry
Research Report	Confluence page	`create_page`	`bmad-research`	`confluence_pages.research_{type}`
Product Brief	Confluence page	`create_page`	`bmad-brief`	`confluence_pages.product_brief`
Brainstorming	Confluence page	`create_page`	`bmad-brainstorming`	`confluence_pages.brainstorming`
Project Context	Confluence page + local	`create_page`	`bmad-project-context`	`confluence_pages.project_context`
Project Documentation	Confluence page	`create_page`	`bmad-documentation`	`confluence_pages.documentation`

Phase 2 -- Planning¶

Artefact	Destination	MCP Tool	Labels	Key Map Entry
PRD	Confluence page	`create_page`	`bmad-prd`	`confluence_pages.prd`
PRD Validation	Confluence inline comments	`createConfluenceInlineComment`	--	--
PRD Edit	Confluence page update	`updateConfluencePage`	--	--
Epics	Jira Epic issues	`create_issue`	`bmad-epic`	`epics.epic-{N}`
Stories	Jira Story issues	`create_issue`	`bmad-story`	`stories.{N}-{M}-{kebab}`
UX Design	Confluence page	`create_page`	`bmad-ux`	`confluence_pages.ux_design`

Epic and Story Linking¶

Stories are linked to Epics via the parent field in createJiraIssue at creation time
PRD and UX Design URLs are added to each Epic's description in a Related Documents section
When default_assignee is configured, the assignee is resolved via lookupJiraAccountId

Phase 3 -- Solutioning¶

Artefact	Destination	MCP Tool	Labels	Key Map Entry
Architecture Decision	Confluence page	`create_page`	`bmad-architecture`	`confluence_pages.architecture`
Readiness Report	Confluence page	`create_page`	`bmad-readiness`	`confluence_pages.readiness_report`

The Readiness Report cross-references PRD, Architecture, and Epics/Stories for completeness. It posts inline comments on PRD and Architecture pages for specific findings.

Phase 4 -- Implementation¶

Artefact	Destination	MCP Tool	Labels
Sprint	Jira Sprint	`jira_create_sprint` (or manual)	--
Story Preparation	Jira Story update + comment	`update_issue` + `add_comment`	`bmad-agent-sm`
Story Tasks	Jira Subtask issues	`create_issue`	`bmad-task`
Dev Story Execution	Jira transitions + comment	`transition_issue` + `add_comment`	`bmad-agent-dev`
Code Review	Jira comment	`add_comment`	`bmad-reviewed`
Retrospective	Confluence page + Jira comment	`create_page` + `add_comment`	`bmad-retrospective`
Course Correction	Jira comments + new issues	`add_comment` + `create_issue`	--
Quick Spec	Jira Story	`create_issue`	`bmad-quick-flow`
Quick Dev	Jira transitions	`transition_issue`	`bmad-quick-flow`

Cross-Agent Communication¶

Artefact	Destination	Description
Adversarial Review	Confluence inline comments or Jira comments	Cynical review of any document
Editorial Review (Prose)	Confluence footer comment	Prose quality review table
Editorial Review (Structure)	Confluence footer comment	Organization analysis with annotations
Edge Case Review	Jira comment	Boundary condition findings with file:line references
Party Mode	Confluence page (optional)	Multi-agent discussion summary
Handoff Notification	Jira comment + label	Structured handoff between agents

Title Conventions¶

All Confluence pages follow the naming pattern:

[{jira_project_key}] {Artefact Type}: {Title}

Examples:

[PROJ] PRD: My Project
[PROJ] Architecture: My Project
[PROJ] Research: Market Analysis