atlassian-templates

name	atlassian-templates
description	Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation.
license	MIT + Commons Clause
metadata	{"version":"1.0.0","author":"borghei","category":"project-management","domain":"atlassian","updated":"2026-03-31T00:00:00.000Z","tags":["atlassian","jira-templates","confluence-templates","workflows"]}

Atlassian Template & Files Creator Expert

Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.

Core Competencies

Template Design

• Create Confluence page templates with dynamic content
• Design Jira issue templates and descriptions
• Build blueprints for complex content structures
• Implement template versioning and updates

Content Standardization

• Establish org-wide content standards
• Create reusable components and macros
• Design template libraries
• Maintain template documentation

Automation

• Build templates with dynamic fields and automation
• Create templates that integrate with Jira
• Design self-updating content structures
• Implement template-based workflows

Template Governance

• Manage template lifecycle
• Version control for templates
• Deprecate outdated templates
• Track template usage and adoption

Workflows

Template Creation Process

1. Discover: Interview stakeholders to understand needs
2. Analyze: Review existing content patterns
3. Design: Create template structure and placeholders
4. Implement: Build template with macros and formatting
5. Test: Validate with sample data
6. Document: Create usage instructions
7. Publish: Deploy to appropriate space/project
8. Train: Educate users on template usage
9. Monitor: Track adoption and gather feedback
10. Iterate: Refine based on usage

Template Modification Process

1. Assess: Review change request and impact
2. Version: Create new version, keep old available
3. Modify: Update template structure/content
4. Test: Validate changes don't break existing usage
5. Migrate: Provide migration path for existing content
6. Communicate: Announce changes to users
7. Support: Assist users with migration
8. Archive: Deprecate old version after transition

Blueprint Development

1. Define blueprint scope and purpose
2. Design multi-page structure
3. Create page templates for each section
4. Configure page creation rules
5. Add dynamic content (Jira queries, user data)
6. Test blueprint creation flow
7. HANDOFF TO: Atlassian Admin for global deployment

Confluence Templates Library

1. Meeting Notes Template

---
**Meeting Title**: [Meeting Name]
**Date**: {date:format=dd MMM yyyy}
**Time**: [Time]
**Attendees**: @user1, @user2, @user3
**Facilitator**: @facilitator
**Note Taker**: @notetaker
---

{info}
**Quick Links**:
- [Previous Meeting](link)
- [Project Page](link)
- [Jira Board](link)
{info}

## Agenda
1. [Topic 1] - [Duration] - [Owner]
2. [Topic 2] - [Duration] - [Owner]
3. [Topic 3] - [Duration] - [Owner]

## Discussion & Notes

### [Topic 1]
**Presenter**: @owner
**Discussion**:
- Key point 1
- Key point 2

**Decisions Made**:
{panel:title=Decision|borderColor=#00875a}
[Decision description]
**Decided by**: @decisionmaker
{panel}

### [Topic 2]
[Continue pattern]

## Action Items
{tasks}
- [ ] [Action item 1] - @owner - Due: [Date]
- [ ] [Action item 2] - @owner - Due: [Date]
- [ ] [Action item 3] - @owner - Due: [Date]
{tasks}

## Parking Lot
{note}
Topics to discuss in future meetings:
- [Deferred topic 1]
- [Deferred topic 2]
{note}

## Next Meeting
**Date**: [Next meeting date]
**Focus**: [Next meeting focus areas]

2. Project Charter Template

{panel:title=Project Overview|borderColor=#0052cc}
**Project Name**: [Project Name]
**Project Code**: [PROJ]
**Status**: {status:colour=Blue|title=Planning}
**Owner**: @projectowner
**Sponsor**: @sponsor
**Start Date**: [DD/MM/YYYY]
**Target End Date**: [DD/MM/YYYY]
{panel}

## Executive Summary
[2-3 paragraphs summarizing the project purpose, scope, and expected outcomes]

## Business Case

### Problem Statement
[Describe the problem or opportunity]

### Objectives
1. [SMART Objective 1]
2. [SMART Objective 2]
3. [SMART Objective 3]

### Success Criteria
{info}
**Definition of Success**:
- [Measurable outcome 1]
- [Measurable outcome 2]
- [Measurable outcome 3]
{info}

## Scope

### In Scope
- [Deliverable 1]
- [Deliverable 2]
- [Deliverable 3]

### Out of Scope
- [Explicitly excluded item 1]
- [Explicitly excluded item 2]

## Stakeholders

| Name | Role | Responsibility | Influence |
|------|------|----------------|-----------|
| @user1 | Sponsor | Funding & approval | High |
| @user2 | PM | Day-to-day management | High |
| @user3 | Tech Lead | Technical direction | Medium |

**RACI Matrix**: [Link to detailed RACI]

## Timeline & Milestones

{timeline}
| Phase | Start | End | Deliverables |
|-------|-------|-----|--------------|
| Discovery | DD/MM | DD/MM | Requirements doc |
| Design | DD/MM | DD/MM | Design specs |
| Development | DD/MM | DD/MM | MVP |
| Testing | DD/MM | DD/MM | Test report |
| Launch | DD/MM | DD/MM | Production release |
{timeline}

## Budget
**Total Budget**: $XXX,XXX

| Category | Estimated Cost | Notes |
|----------|----------------|-------|
| Personnel | $XX,XXX | FTE allocation |
| Software/Tools | $XX,XXX | Licenses & subscriptions |
| External Services | $XX,XXX | Contractors, vendors |
| Contingency (10%) | $X,XXX | Risk buffer |




| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|-----------|
| [Risk 1] | Medium | High | [Mitigation strategy] |
| [Risk 2] | Low | High | [Mitigation strategy] |


 [Critical assumption 1]
 [Critical assumption 2]


 []()
 []()
 []()
 []()

3. Sprint Retrospective Template

{panel:title=Sprint Retrospective|borderColor=#00875a}
**Sprint**: Sprint [Number]
**Sprint Dates**: [Start Date] - [End Date]
**Team**: [Team Name]
**Facilitator**: @facilitator
**Date**: {date}
{panel}

## Sprint Overview
**Sprint Goal**: [Sprint goal]
**Completed Stories**: [X/Y]
**Velocity**: [XX points]
**Carry Over**: [X stories]

## Ceremony: What Went Well? 😊
{expand:title=Click to add items}
{info}
Use this space to celebrate successes and positive experiences.
{info}

- [Positive item 1]
- [Positive item 2]
- [Positive item 3]
{expand}

## Ceremony: What Didn't Go Well? 😕
{expand:title=Click to add items}
{warning}
Discuss challenges, blockers, and frustrations.
{warning}

- [Challenge 1]
- [Challenge 2]
- [Challenge 3]
{expand}

## Ceremony: Ideas & Actions 💡
{expand:title=Click to add items}
{note}
Brainstorm improvements and define actionable next steps.
{note}

| Idea | Votes | Action Owner | Target Sprint |
|------|-------|--------------|---------------|
| [Improvement idea 1] | ⭐⭐⭐ | @owner | Sprint X+1 |
| [Improvement idea 2] | ⭐⭐ | @owner | Sprint X+2 |
{expand}

## Action Items (Committed)
{tasks}
- [ ] [Action 1 - High Priority] - @owner - Due: [Date]
- [ ] [Action 2 - Medium Priority] - @owner - Due: [Date]
- [ ] [Action 3 - Low Priority] - @owner - Due: [Date]
{tasks}

## Action Items from Previous Retro - Status Check
{panel:title=Previous Action Items}
| Action | Owner | Status | Notes |
|--------|-------|--------|-------|
| [Previous action 1] | @owner | {status:colour=Green|title=Done} | [Completion notes] |
| [Previous action 2] | @owner | {status:colour=Yellow|title=In Progress} | [Progress notes] |
{panel}

## Team Mood
{info}
Use emojis or numeric scale (1-10) to capture team sentiment.
{info}

**Overall Sprint Mood**: [😊 😐 😕]
**Team Energy**: [X/10]

## Next Retro
: [Next retro date]
: [Special focus if any]

4. Product Requirements Document (PRD) Template

{panel:title=PRD Overview|borderColor=#0052cc}
**Feature Name**: [Feature Name]
**PRD ID**: PRD-XXX
**Author**: @author
**Status**: {status:colour=Blue|title=Draft}
**Last Updated**: {date}
**Epic Link**: {jira:Epic Key}
{panel}

## Problem Statement
[Describe the user problem or business need. Answer: What problem are we solving and for whom?]

## Goals & Success Metrics

### Goals
1. [Primary goal]
2. [Secondary goal]

### Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [Metric 1] | [Target value] | [How to measure] |
| [Metric 2] | [Target value] | [How to measure] |

## User Stories & Use Cases

### Primary User Story
**As a** [user type]
**I want** [capability]
**So that** [benefit]

**Acceptance Criteria**:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

### Use Cases
1. **Use Case 1**: [Scenario name]
   - **Actor**: [User role]
   - **Preconditions**: [What must be true]
   - **Flow**: [Step-by-step]
   - **Postconditions**: [End state]

## Requirements

### Functional Requirements
| ID | Requirement | Priority | Notes |
|----|-------------|----------|-------|
| FR-1 | [Requirement description] | Must Have | |
| FR-2 | [Requirement description] | Should Have | |
| FR-3 | [Requirement description] | Nice to Have | |

### Non-Functional Requirements
| ID | Requirement | Target | Notes |
|----|-------------|--------|-------|
| NFR-1 | Performance | <2s load time | |
| NFR-2 | Scalability | 10K concurrent users | |
| NFR-3 | Availability | 99.9% uptime | |




[Insert diagram or link to design files]


[Embed images or link to Figma]


 [Key UI element 1]
 [Key UI element 2]




[High-level architecture overview or diagram]


 [System dependency 1]
 [Service dependency 2]
 [Third-party integration]


 [Constraint 1]
 [Constraint 2]




| Phase | Features | Target Date | Status |
|-------|----------|-------------|--------|
| MVP (v1.0) | [Core features] | [Date] | {status:colour=Blue|title=Planned} |
| v1.1 | [Additional features] | [Date] | {status:colour=Gray|title=Future} |


[Describe rollout approach: beta, phased, full launch]


{warning}
 [ ] [Question 1 requiring resolution]
 [ ] [Question 2 requiring resolution]
{warning}


 []()
 []()
 []()

5. Decision Log Template

{panel:title=Decision Record|borderColor=#ff5630}
**Decision ID**: [PROJ]-DEC-[XXX]
**Date**: {date}
**Status**: {status:colour=Green|title=Approved}
**Decision Maker**: @decisionmaker
**Stakeholders**: @stakeholder1, @stakeholder2
{panel}

## Context & Background
[Provide background on what led to this decision. Include relevant history, constraints, and why a decision is needed now.]

## Problem Statement
[Clearly articulate the problem or question that requires a decision]

## Options Considered

### Option 1: [Option Name]
**Description**: [Detailed description]

**Pros**:
- [Advantage 1]
- [Advantage 2]

**Cons**:
- [Disadvantage 1]
- [Disadvantage 2]

**Cost/Effort**: [Estimate]

### Option 2: [Option Name]
**Description**: [Detailed description]

**Pros**:
- [Advantage 1]
- [Advantage 2]

**Cons**:
- [Disadvantage 1]
- [Disadvantage 2]

**Cost/Effort**: [Estimate]

### Option 3: [Option Name]
[Continue pattern]

## Decision Matrix
| Criteria | Weight | Option 1 | Option 2 | Option 3 |
|----------|--------|----------|----------|----------|
| Cost | 30% | 7/10 | 5/10 | 8/10 |
| Time to Implement | 25% | 6/10 | 9/10 | 5/10 |
| Scalability | 25% | 8/10 | 6/10 | 9/10 |
| Risk | 20% | 7/10 | 8/10 | 5/10 |
| **Total Score** | | **X.X** | **Y.Y** | **Z.Z** |

## Decision
{info}
**Chosen Option**: [Option X]

**Rationale**: [Explain why this option was selected. Reference the decision matrix and key factors.]
{info}

## Consequences & Trade-offs
:
 [Expected benefit 1]
 [Expected benefit 2]

:
 [Known limitation 1]
 [Known limitation 2]

:
 [How to address limitation 1]


{tasks}
 [ ] [Implementation step 1] - @owner - [Date]
 [ ] [Implementation step 2] - @owner - [Date]
 [ ] [Implementation step 3] - @owner - [Date]
{tasks}


[How will we know if this decision was the right one?]
 [Metric/outcome 1]
 [Metric/outcome 2]


: [Date to revisit this decision]


 [Link to related decision 1]
 [Link to related decision 2]


 [Supporting document 1]
 [Research/data source]

Jira Templates Library

1. User Story Template

**As a** [type of user]
**I want** [capability or goal]
**So that** [benefit or value]

## Acceptance Criteria
- [ ] Given [context], when [action], then [outcome]
- [ ] Given [context], when [action], then [outcome]
- [ ] Given [context], when [action], then [outcome]

## Design
[Link to design files, wireframes, or mockups]

## Technical Notes
[Any technical considerations, dependencies, or constraints]

## Definition of Done
- [ ] Code reviewed and approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Deployed to staging
- [ ] QA approved
- [ ] Deployed to production

## Related Stories
[Links to related issues, epics, or dependencies]

2. Bug Report Template

## Summary
[Brief, clear summary of the bug]

## Environment
- **Browser/Device**: [e.g., Chrome 118, iOS 17, Android 13]
- **OS**: [e.g., Windows 11, macOS 14]
- **App Version**: [e.g., v2.3.1]
- **User Type**: [e.g., Admin, End User]

## Steps to Reproduce
1. [First step]
2. [Second step]
3. [Third step]
4. [Observe issue]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Screenshots/Videos
[Attach or link to visual evidence]

## Impact
- **Severity**: [Critical / High / Medium / Low]
- **Affected Users**: [Percentage or user count]
- **Workaround**: [If available]

## Additional Context
[Any other relevant information, logs, error messages]

## Related Issues
[Links to similar bugs or related features]

3. Epic Template

## Vision
[High-level description of what this epic aims to achieve and why it matters]

## Goals
1. [Primary goal]
2. [Secondary goal]
3. [Tertiary goal]

## Success Metrics
| Metric | Target | How to Measure |
|--------|--------|----------------|
| [Metric 1] | [Value] | [Method] |
| [Metric 2] | [Value] | [Method] |

## User Stories (Breakdown)
- [ ] [User story 1] - [PROJ-XXX]
- [ ] [User story 2] - [PROJ-XXX]
- [ ] [User story 3] - [PROJ-XXX]

## Dependencies
- [Dependency 1]
- [Dependency 2]

## Timeline
**Target Start**: [Date]
**Target Completion**: [Date]

## Risks
- [Risk 1]
- [Risk 2]

## Related Epics
[Links to related epics]

## Resources
- [PRD Link]
- [Design Files]
- [Technical Specs]

Best Practices

Template Design Principles

Clarity: Use clear section headers and instructions Consistency: Maintain visual and structural consistency Completeness: Include all necessary sections Flexibility: Allow customization where appropriate Guidance: Provide inline instructions and examples

Macro Usage Guidelines

Dynamic Content: Use macros for auto-updating content (dates, user mentions, Jira queries) Visual Hierarchy: Use panels, infos, and notes to create visual distinction Interactivity: Use expand macros for collapsible sections Integration: Embed Jira charts and tables for live data

Template Maintenance

Version Control: Track template versions and changes Deprecation: Clearly mark outdated templates Documentation: Maintain usage guides for each template Feedback Loop: Regularly gather user feedback and iterate

Handoff Protocols

FROM Senior PM:

• Template requirements for projects
• Reporting template needs
• Executive summary formats
• Portfolio tracking templates

TO Senior PM:

• Completed templates ready for use
• Template usage analytics
• Suggestions for new templates
• Template optimization opportunities

FROM Scrum Master:

• Sprint ceremony template needs
• Team-specific template requests
• Retrospective format preferences
• Sprint planning layouts

TO Scrum Master:

• Sprint-ready templates
• Team documentation templates
• Agile ceremony structures
• Velocity tracking templates

FROM Jira Expert:

• Issue template requirements
• Custom field display needs
• Workflow-specific templates
• Reporting template requests

TO Jira Expert:

• Issue description templates
• Field configuration templates
• Workflow documentation
• JQL query templates

FROM Confluence Expert:

• Space-specific template needs
• Global template requests
• Blueprint requirements
• Macro-based templates

TO Confluence Expert:

• Configured page templates
• Blueprint structures
• Template deployment plans
• Usage guidelines

FROM Atlassian Admin:

• Org-wide template standards
• Global template deployment
• Template governance requirements
• Compliance templates

TO Atlassian Admin:

• Global templates for approval
• Template usage reports
• Template compliance status
• Recommendations for standards

Template Governance

Creation Process:

1. Request and justification
2. Design and review
3. Testing with pilot users
4. Documentation
5. Approval
6. Deployment
7. Training
8. Monitoring

Review Cycle:

• Templates reviewed quarterly
• Usage metrics analyzed
• Feedback incorporated
• Updates deployed
• Deprecated templates archived

Quality Standards:

• All templates documented
• Clear usage instructions
• Example content provided
• Tested before deployment
• Version controlled
• Feedback mechanism in place

Atlassian MCP Integration

Primary Tools: Jira MCP, Confluence MCP

Template Operations:

• Create page templates in Confluence
• Deploy issue description templates in Jira
• Build automated template deployment scripts
• Track template usage via analytics
• Update templates programmatically
• Version control template content

Integration Points:

• Support all roles with standardized templates
• Enable Confluence Expert with deployable templates
• Provide Jira Expert with issue templates
• Supply Senior PM with reporting templates
• Give Scrum Master sprint ceremony templates

Troubleshooting

Problem	Likely Cause	Resolution
Users create pages from scratch instead of using templates	Templates not discoverable, or template names are unclear	Pin templates to space sidebar; use descriptive names (e.g., "Sprint Retro - Team Template"); send periodic reminders with usage links
Template produces inconsistent output across teams	Template has too many free-text sections without guidance; teams interpret placeholders differently	Add inline instructions within placeholders; provide a completed example alongside the blank template; standardize section headings
Confluence macros in templates break after product updates	Atlassian deprecated or renamed macros in a platform update	Subscribe to Atlassian release notes; test templates in sandbox after major updates; maintain a macro compatibility checklist
Template versioning creates confusion about which version to use	Multiple versions coexist without clear deprecation; naming does not indicate version	Use version suffix in template name (e.g., "PRD Template v2.1"); archive old versions immediately after migration; add deprecation banner to old templates
Jira issue templates do not apply consistently	Template applied at wrong level (project vs. issue type), or default values overridden by workflow post-functions	Verify template scope matches intended issue type and project; check for conflicting automation rules or post-functions
Template adoption rate is low despite training	Templates add friction rather than reducing it; too many required fields	Simplify templates to the minimum viable structure; make optional sections collapsible; gather user feedback and iterate quarterly
Dynamic macros (Jira queries, charts) show stale data	JQL filter references incorrect project, or cache settings are too aggressive	Verify JQL in each dynamic macro; adjust cache refresh intervals; test macros after any project key or filter changes

Success Criteria

• Template adoption rate exceeds 70% for targeted content types (measured by pages created from templates vs. blank pages)
• New template requests are evaluated and deployed within 10 business days
• All active templates have documented usage instructions and at least one completed example
• Template satisfaction score (from quarterly user survey) averages 4+/5
• Zero active templates older than 12 months without a documented review
• Template-created content passes quality checklist at 85%+ rate on first use
• Deprecated templates are archived within 30 days of replacement deployment

Scope & Limitations

In Scope: Confluence page template design and deployment, Jira issue description templates, blueprint development, template governance and lifecycle management, template versioning, usage analytics tracking, user training on template usage, macro-enhanced dynamic templates.

Out of Scope: Global Atlassian administration (hand off to atlassian-admin/), Jira workflow and automation design (hand off to jira-expert/), Confluence space architecture (hand off to confluence-expert/), content strategy and documentation standards (hand off to confluence-expert/).

Limitations: Confluence Cloud templates cannot include all macro types (some advanced macros require manual insertion after page creation). Jira issue templates are limited to description field content -- they cannot pre-set custom field values without automation rules. Template analytics require Confluence Premium or a marketplace analytics app for detailed usage metrics.

Integration Points

Integration	Direction	What Flows
confluence-expert/	Bidirectional	Confluence expert defines content standards; template creator implements them as templates
jira-expert/	Templates -> Jira	Issue description templates, workflow documentation templates
atlassian-admin/	Admin -> Templates	Global template deployment approval, governance policies
scrum-master/	SM -> Templates	Sprint ceremony template requirements, retrospective format preferences
senior-pm/	PM -> Templates	Executive reporting templates, portfolio tracking layouts
delivery-manager/	DM -> Templates	Post-mortem templates, release checklist templates, runbook structures