Templates¶

Document templates used by agents when creating Confluence pages and Jira issues. Templates live in _bmad/atlassian/templates/ and provide consistent structure for all BMAD artefacts.

Template Reference¶

Template	File	Used By	Output
Product Brief	`product-brief-template.md`	Analyst (Mary)	Confluence page
Research Report	`research-template.md`	Analyst (Mary)	Confluence page
PRD	`prd-template.md`	PM (John)	Confluence page
Epics	`epics-template.md`	PM (John)	Jira Epic + Story structure
Story	`story-template.md`	SM (Bob)	Jira Story description
UX Design	`ux-design-template.md`	UX Designer (Sally)	Confluence page
Architecture Decision	`architecture-decision-template.md`	Architect (Winston)	Confluence page
Readiness Report	`readiness-report-template.md`	Architect (Winston) / SM (Bob)	Confluence page
Brainstorming Session	`brainstorming-template.md`	Analyst (Mary)	Confluence page
Project Context	`project-context-template.md`	Analyst (Mary)	Confluence page
Tech Spec	`tech-spec-template.md`	Quick Flow (Barry)	Jira Story description
Doc: Source Tree	`document-project-source-tree.md`	Tech Writer (Paige)	Confluence page
Doc: Overview	`document-project-overview.md`	Tech Writer (Paige)	Confluence page
Doc: Index	`document-project-index.md`	Tech Writer (Paige)	Confluence page
Doc: Deep Dive	`document-project-deep-dive.md`	Tech Writer (Paige)	Confluence page
Acceptance Criteria	`story-acceptance-criteria-template.md`	PM (John) / SM (Bob)	Jira Story AC format

How Templates Are Used¶

Templates are referenced in the artefact mapping (artefact-mapping.yaml) and workflow instructions. Agents use templates as structural guides rather than filling in blanks:

Agent loads the template structure
Content is generated through the agent's workflow (interviews, analysis, research)
The template ensures consistent sections, headings, and formatting
Output is written to Confluence via the write-to-confluence task or to Jira via createJiraIssue

Key Templates¶

PRD Template¶

The PRD template structures the Product Requirements Document with sections for:

Executive summary
Problem statement
User personas
Functional requirements
Non-functional requirements
Success metrics
Out of scope

Story Template¶

The Story template structures Jira Story descriptions with:

User story statement (As a... I want... So that...)
Acceptance criteria (Given/When/Then)
Technical notes
Dependencies
Task breakdown

Architecture Decision Template¶

The Architecture Decision template structures technical decisions with:

Context and problem statement
Decision drivers
Considered options with trade-offs
Decision outcome
Consequences (positive and negative)