atlassian-templates

安装量: 48
排名: #15439

安装

npx skills add https://github.com/alirezarezvani/claude-skills --skill atlassian-templates
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
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
Document
Create usage instructions
Publish
Deploy to appropriate space/project
Train
Educate users on template usage
Monitor
Track adoption and gather feedback
Iterate
Refine based on usage
Template Modification Process
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
Migrate
Provide migration path for existing content
Communicate
Announce changes to users
Support
Assist users with migration
Archive
Deprecate old version after transition
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
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 - Project Page - Jira Board

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

[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]

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

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]

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]

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 |

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 |

Risks & Assumptions

Top Risks | Risk | Probability | Impact | Mitigation | |


|

|

|

| | [Risk 1] | Medium | High | [Mitigation strategy] | | [Risk 2] | Low | High | [Mitigation strategy] |

Assumptions

[Critical assumption 1]

[Critical assumption 2]

[ Jira Project ](

)

[ Confluence Space ](

)

[ Design Files ](

)

[ Technical Docs ](

)
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}

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]

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]

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 |

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]

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] |

Team Mood
{info}
Use emojis or numeric scale (1-10) to capture team sentiment.
{info}
**
Overall Sprint Mood
**
[😊 😐 😕]
**
Team Energy
**
[X/10]

Next Retro
**
Date
**
[Next retro date]
**
Focus
**
[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}

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 | |

Design & User Experience

User Flow [Insert diagram or link to design files]

Wireframes/Mockups [Embed images or link to Figma]

UI Specifications

[Key UI element 1]

[Key UI element 2]

Technical Considerations

Architecture [High-level architecture overview or diagram]

Dependencies

[System dependency 1]

[Service dependency 2]

[Third-party integration]

Technical Constraints

[Constraint 1]

[Constraint 2]

Release Plan

Phases | 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} |

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

Open Questions {warning} - [ ] [ Question 1 requiring resolution ] - [ ] [ Question 2 requiring resolution ]

Appendix

[ Related Documents ](

)

[ Research & Data ](

)

[ Competitive Analysis ](

)
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

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.]

Consequences & Trade-offs ** Positive Consequences ** : - [Expected benefit 1] - [Expected benefit 2] ** Negative Consequences/Trade-offs ** : - [Known limitation 1] - [Known limitation 2] ** Mitigation Plans ** : - [How to address limitation 1]

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

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

Review Date
**
Scheduled Review
**
[Date to revisit this decision]

[Link to related decision 2]

References

[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

[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]

[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
:
Request and justification
Design and review
Testing with pilot users
Documentation
Approval
Deployment
Training
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
返回排行榜