borghei/Claude-Skills / project-management/atlassian-templates
atlassian-templates
VerifiedBuilds, validates and retires reusable Jira issue and Confluence page templates. Use when creating a team or org-wide template, a template is ignored or half-filled, or a template library has sprawled. Space layout is confluence-expert.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.7 KB |
| assets/sample_template.json | config | 901 B |
| assets/sample_template_flawed.json | config | 371 B |
| assets/sample_template_spec.json | config | 1.1 KB |
| assets/sample_template_usage.json | config | 950 B |
| examples/unified-prd-epic-story-rollout.md | markdown | 11.5 KB |
| references/confluence-templates.md | markdown | 10.1 KB |
| references/jira-templates.md | markdown | 2.4 KB |
| references/red-flags.md | markdown | 12.9 KB |
| references/troubleshooting.md | markdown | 2.8 KB |
| references/workflows-and-governance.md | markdown | 5.3 KB |
| scripts/template_scaffolder.py | script | 7.6 KB |
| scripts/template_usage_analyzer.py | script | 7.5 KB |
| scripts/template_validator.py | script | 8.3 KB |
references/troubleshooting.md
View on GitHub# Troubleshooting & Success Criteria
Read this when a deployed template is misbehaving (low adoption, broken macros, version confusion, stale data) or when you need the measurable bar for "this skill did its job."
## 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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |