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.
Workflows
Template Creation Process
- 1. Discover: Interview stakeholders to understand needs
- Analyze: Review existing content patterns
- Design: Create template structure and placeholders
- Implement: Build template with macros and formatting
- Test: Validate with sample data — confirm template renders correctly in preview before publishing
- Document: Create usage instructions
- Publish: Deploy to appropriate space/project via MCP (see MCP Operations below)
- Verify: Confirm deployment success; roll back to previous version if errors occur
- Train: Educate users on template usage
- Monitor: Track adoption and gather feedback
- Iterate: Refine based on usage
Template Modification Process
- 1. Assess: Review change request and impact
- Version: Create new version, keep old available
- Modify: Update template structure/content
- Test: Validate changes don't break existing usage; preview updated template before publishing
- Migrate: Provide migration path for existing content
- Communicate: Announce changes to users
- Support: Assist users with migration
- Archive: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted
Blueprint Development
- 1. Define blueprint scope and purpose
- Design multi-page structure
- Create page templates for each section
- Configure page creation rules
- Add dynamic content (Jira queries, user data)
- Test blueprint creation flow end-to-end with a sample space
- Verify all macro references resolve correctly before deployment
- HANDOFF TO: Atlassian Admin for global deployment
Confluence Templates Library
See TEMPLATES.md for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.
Confluence Template Types
| Template | Purpose | Key Macros Used |
|---|
| Meeting Notes | Structured meeting records with agenda, decisions, and action items | INLINECODE0 , {tasks}, {panel}, {info}, INLINECODE4 |
| Project Charter |
Org-level project scope, stakeholder RACI, timeline, and budget |
{panel},
{status},
{timeline},
{info} |
|
Sprint Retrospective | Agile ceremony template with What Went Well / Didn't Go Well / Actions |
{panel},
{expand},
{tasks},
{status} |
|
PRD | Feature definition with goals, user stories, functional/non-functional requirements, and release plan |
{panel},
{status},
{jira},
{warning} |
|
Decision Log | Structured option analysis with decision matrix and implementation tracking |
{panel},
{status},
{info},
{tasks} |
Standard Sections included across all Confluence templates:
- - Header panel with metadata (owner, date, status)
- Clearly labelled content sections with inline placeholder instructions
- Action items block using
{tasks} macro - Related links and references
Complete Example: Meeting Notes Template
The following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):
CODEBLOCK0
Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in TEMPLATES.md.
Jira Templates Library
Jira Template Types
| Template | Purpose | Key Sections |
|---|
| User Story | Feature requests in As a / I want / So that format | Acceptance Criteria (Given/When/Then), Design links, Technical Notes, Definition of Done |
| Bug Report |
Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |
|
Epic | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |
Standard Sections included across all Jira templates:
- - Clear summary line
- Acceptance or success criteria as checkboxes
- Related issues and dependencies block
- Definition of Done (for stories)
Macro Usage Guidelines
Dynamic Content: Use macros for auto-updating content (dates, user mentions, Jira queries)
Visual Hierarchy: Use {panel}, {info}, and {note} to create visual distinction
Interactivity: Use {expand} for collapsible sections in long templates
Integration: Embed Jira charts and tables via {jira} macro for live data
Atlassian MCP Integration
Primary Tools: Confluence MCP, Jira MCP
Template Operations via MCP
All MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.
Create a Confluence page template:
CODEBLOCK1
Update an existing template:
CODEBLOCK2
Create a Jira issue description template (via field configuration):
CODEBLOCK3
Deploy template to multiple spaces (batch):
CODEBLOCK4
Validation checkpoint after deployment:
- - Retrieve the created/updated page and assert it renders without macro errors
- Check that
{jira} embeds resolve against the target Jira project - Confirm
{tasks} blocks are interactive in the published view - If any check fails: revert using
confluence_update_page with version: <current + 1> and the previous version body
Best Practices & Governance
Org-Specific Standards:
- - Track template versions with version notes in the page header
- Mark outdated templates with a
{warning} banner before archiving; archive (do not delete) - Maintain usage guides linked from each template
- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating
Quality Gates (apply before every deployment):
- - Example content provided for each section
- Tested with sample data in preview
- Version comment added to change log
- Feedback mechanism in place (comments enabled or linked survey)
Governance Process:
- 1. Request and justification
- Design and review
- Testing with pilot users
- Documentation
- Approval
- Deployment (via MCP or manual)
- Training
- Monitoring
Handoff Protocols
See HANDOFFS.md for the full handoff matrix. Summary:
| Partner | Receives FROM | Sends TO |
|---|
| Senior PM | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |
| Scrum Master |
Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |
|
Jira Expert | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |
|
Confluence Expert | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |
|
Atlassian Admin | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |
Atlassian 模板与文件创建专家
专门为 Jira 和 Confluence 创建、修改和管理可复用模板与文件的专家。确保一致性、加速内容创建，并维护组织级标准。
工作流程
模板创建流程
- 1. 发现：与利益相关者访谈以了解需求
- 分析：审查现有内容模式
- 设计：创建模板结构和占位符
- 实施：使用宏和格式构建模板
- 测试：使用样本数据进行验证——在发布前确认模板预览渲染正确
- 文档化：创建使用说明
- 发布：通过 MCP 部署到相应空间/项目（参见下方的 MCP 操作）
- 验证：确认部署成功；如果出现错误则回滚到上一版本
- 培训：教育用户如何使用模板
- 监控：跟踪采用情况并收集反馈
- 迭代：根据使用情况进行优化
模板修改流程
- 1. 评估：审查变更请求及其影响
- 版本管理：创建新版本，保留旧版本可用
- 修改：更新模板结构/内容
- 测试：验证更改不会破坏现有使用；在发布前预览更新后的模板
- 迁移：为现有内容提供迁移路径
- 沟通：向用户宣布变更
- 支持：协助用户进行迁移
- 归档：过渡期后弃用旧版本；确认已弃用的模板被取消列出而非删除
蓝图开发
- 1. 定义蓝图范围和目的
- 设计多页面结构
- 为每个部分创建页面模板
- 配置页面创建规则
- 添加动态内容（Jira 查询、用户数据）
- 使用示例空间端到端测试蓝图创建流程
- 在部署前验证所有宏引用是否正确解析
- 交接给：Atlassian 管理员进行全局部署
Confluence 模板库
请参阅 TEMPLATES.md 获取完整的参考表格和可直接复制粘贴的模板结构。以下总结了此技能创建和维护的标准类型。
Confluence 模板类型
| 模板 | 用途 | 使用的主要宏 |
|---|
| 会议记录 | 结构化的会议记录，包含议程、决策和行动项 | {date}, {tasks}, {panel}, {info}, {note} |
| 项目章程 |
组织级项目范围、利益相关者 RACI、时间线和预算 | {panel}, {status}, {timeline}, {info} |
|
冲刺回顾 | 敏捷仪式模板，包含做得好的/做得不好的/行动项 | {panel}, {expand}, {tasks}, {status} |
|
PRD | 功能定义，包含目标、用户故事、功能/非功能需求和发布计划 | {panel}, {status}, {jira}, {warning} |
|
决策日志 | 结构化的选项分析，包含决策矩阵和实施跟踪 | {panel}, {status}, {info}, {tasks} |
所有 Confluence 模板包含的标准部分：
- - 包含元数据的标题面板（负责人、日期、状态）
- 带有内联占位符说明的清晰标记内容部分
- 使用 {tasks} 宏的行动项块
- 相关链接和参考资料
完整示例：会议记录模板
以下是 Confluence 存储格式（wiki 标记）中可直接复制粘贴的会议记录模板：
{panel:title=会议元数据|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}
日期： {date}
负责人/主持人： @[主持人姓名]
参会者： @[姓名], @[姓名]
状态： {status:colour=Yellow|title=进行中}
{panel}
h2. 议程
[议程项 1]
[议程项 2]
[议程项 3]
h2. 讨论与决策
{panel:title=关键决策|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}
- 决策 1： [决策内容及原因]
- 决策 2：* [决策内容及原因]
{panel}
{info:title=备注}
[详细的讨论笔记、背景信息或上下文]
{info}
h2. 行动项
{tasks}
- * [ ] [行动项] — 负责人：@[姓名] — 截止日期：{date}
- [ ] [行动项] — 负责人：@[姓名] — 截止日期：{date}
{tasks}
h2. 后续步骤与相关链接
- * 下次会议：{date}
- 相关页面：[链接]
- 相关 Jira 问题：{jira:key=PROJ-123}
所有其他模板类型（项目章程、冲刺回顾、PRD、决策日志）和所有 Jira 模板的完整示例可根据要求生成，或参见 TEMPLATES.md。
Jira 模板库
Jira 模板类型
| 模板 | 用途 | 关键部分 |
|---|
| 用户故事 | 以作为/我想要/以便格式提出的功能请求 | 验收标准（Given/When/Then）、设计链接、技术说明、完成定义 |
| 缺陷报告 |
带有复现步骤的缺陷捕获 | 环境、复现步骤、预期与实际行为、严重程度、临时解决方案 |
|
史诗 | 高层级倡议范围 | 愿景、目标、成功指标、故事分解、依赖关系、时间线 |
所有 Jira 模板包含的标准部分：
- - 清晰的摘要行
- 以复选框形式呈现的验收或成功标准
- 相关问题与依赖关系块
- 完成定义（针对故事）
宏使用指南
动态内容：使用宏实现自动更新内容（日期、用户提及、Jira 查询）
视觉层次：使用 {panel}、{info} 和 {note} 创建视觉区分
交互性：在长模板中使用 {expand} 实现可折叠部分
集成：通过 {jira} 宏嵌入 Jira 图表和表格以获取实时数据
Atlassian MCP 集成
主要工具：Confluence MCP、Jira MCP
通过 MCP 进行模板操作
以下所有 MCP 调用使用 Atlassian MCP 服务器期望的确切参数名称。在执行前将尖括号占位符替换为实际值。
创建 Confluence 页面模板：
json
{
tool: confluencecreatepage,
parameters: {
space_key: PROJ,
title: 模板：会议记录,
body: <存储格式模板内容>,
labels: [template, meeting-notes],
parent_id: <可选父页面 ID>
}
}
更新现有模板：
json
{
tool: confluenceupdatepage,
parameters: {
page_id: <现有页面 ID>,
version: <当前版本 + 1>,
title: 模板：会议记录,
body: <更新后的存储格式内容>,
version_comment: v2 — 在标题中添加了状态宏
}
}
创建 Jira 问题描述模板（通过字段配置）：
json
{
tool: jiraupdatefield_configuration,
parameters: {
project_key: PROJ,
field_id: description,
default_value: <模板 Markdown 或 Atlassian 文档格式 JSON>
}
}
将模板部署到多个空间（批量）：
json
// 对每个目标空间键重复
{
tool: confluencecreatepage,
parameters: {
spacekey: KEY>,
title: 模板：会议记录,
body: <存储格式模板内容>,
labels: [template]
}
}
// 每次创建后，验证：
{
tool: confluencegetpage,
parameters: {
spacekey: KEY>,
title: 模板：会议记录
}
}
// 在继续下一个空间之前，断言响应状态 == 200 且页面正文非空
部署后的验证检查点：
- - 检索已创建/更新的页面，并断言其渲染无宏错误
- 检查 {jira} 嵌入是否解析到目标 Jira 项目
- 确认 {tasks} 块在已发布视图中可交互
- 如果任何检查失败：使用 confluenceupdatepage 并设置 version: <当前 + 1> 和上一版本的正文进行回滚
##
