This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
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
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
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
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
{date}, {tasks}, {panel}, {info}, {note}
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):
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 Jira issue description template (via field configuration):
{
"tool": "jira_update_field_configuration",
"parameters": {
"project_key": "PROJ",
"field_id": "description",
"default_value": "<template markdown or Atlassian Document Format JSON>"
}
}
Deploy template to multiple spaces (batch):
// Repeat for each target space key
{
"tool": "confluence_create_page",
"parameters": {
"space_key": "<SPACE_KEY>",
"title": "Template: Meeting Notes",
"body": "<storage-format template content>",
"labels": ["template"]
}
}
// After each create, verify:
{
"tool": "confluence_get_page",
"parameters": {
"space_key": "<SPACE_KEY>",
"title": "Template: Meeting Notes"
}
}
// Assert response status == 200 and page body is non-empty before proceeding to next space
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:
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:
