Confluence and Jira Template Builder
Build one Confluence or Jira template people actually fill in: real-example structure, placeholders, roll-up reports, required fields.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you build a bug triage template for Jira. You'd want to include fields for severity, priority, and maybe some descriptors of what the bug is. You could also add fields for the affected component or team. To make this really useful for your workflow, I'd want to understand how your team currently triages bugs. What information matters most to your team—is it severity, impact, affected users? Do you want to route bugs to specific teams based on component? Are there approval steps or SLAs around triage? Once I know more about your process, I can design a template that fits your needs.
BUG TRIAGE TEMPLATE: Jira Custom Workflow
CUSTOM FIELDS
1. Severity (Dropdown) - Controls SLA and escalation path
Critical (60-min response), High (4-hour), Medium (24-hour), Low (5-day)
Affects escalation automation and alert rules
2. Business Impact (Select List) - Determines priority
Revenue impact: None, 1-10 accounts, 10-50 accounts, 50+ accounts
Used in priority calculation algorithm
3. Root Cause Category (Dropdown) - For pattern analysis
Infrastructure, Data model, Third-party API, Configuration, Feature defect
Route to Platform team, Database team, Integrations team, Config team, or Product team
4. Affected Component (Select List) - Links to product architecture
API, Frontend, Database, Mobile App, Admin Panel, Integrations
5. Estimated Impact Radius (Radio) - Scope understanding
Single account, Region, All customers, Specific user segment
AUTOMATION RULES
Rule 1: Auto-escalate Critical severity bugs
Trigger: Issue type = Bug AND Severity = Critical
Action: Assign to Platform Escalation Queue, Post to Slack #critical-bugs, Set SLA to 60 minutes
Rule 2: Reject incomplete bug reports
Trigger: Issue missing Root Cause Category, Business Impact, or Reproduction Steps
Action: Move to "Awaiting Details" status, Comment: "Please complete triage fields", Notify Reporter
Rule 3: Auto-route by component
Trigger: Issue Affected Component = API
Action: Assign to API team, Set sprint to API team's current sprint (if available)
TRIAGE WORKFLOW (5-state)
1. New Bug → Triage (Team fills: Severity, Business Impact, Component, Reproduction Steps)
2. Triage → Classified (Engineering lead validates field quality)
3. Classified → Scheduled or Rejected (If incomplete, moves to Awaiting Details, loops back)
4. Scheduled → In Progress (Dev picks up, linked to story)
5. In Progress → Done (Fix verified, linked to release)
TRIAGE CHECKLIST (On-screen guide)
Required on New:
□ Reproducible step-by-step? (If no, ask reporter for clarity)
□ Severity: Is this blocking anyone's workflow? (Yes = High minimum)
□ Business Impact: How many customers affected? (Needed for priority)
□ Component: Which system is broken?
□ Environment: Production, Staging, Dev?
□ Screenshot or video: If visual issue, must have proof
Optional but helpful:
□ Affected versions (if applies)
□ Related bugs (link to similar issues)
□ Workaround (if exists)
SCORING ALGORITHM (Auto-calculates Priority)
Priority Score = (Severity weight × 0.5) + (Business Impact weight × 0.3) + (Frequency weight × 0.2)
Score 9-10 = P0 (Fix immediately)
Score 7-8 = P1 (Fix this sprint)
Score 4-6 = P2 (Fix next sprint)
Score 1-3 = P3 (Backlog)
REPORTING & INSIGHTS
Dashboard view: Bugs by Component over time (identify patterns)
SLA compliance: What % of Critical bugs were triaged within 60 min
Root cause trends: Are more bugs in API or Database this month
Triage quality: What % of bugs have all required fields filledAbout this skill
A template is only worth having if people use it and the results roll up somewhere useful. This skill derives the structure from your real examples, keeps required parts minimal, and tests the template by filling it in once.
What it does
- Derives required, conditional, and optional sections from 2-3 real documents or tickets
- Adds instructional placeholders written as example answers, not 'insert text here'
- Puts metadata in a Page Properties block with a label so every instance appears in one live report table
- Fakes Jira issue templates reliably with an automation rule, and sets required fields and screens without blocking creation
- Flags adoption traps: too many required fields, stale placeholders, template drift
What you get
The template, where and how to install it, the roll-up index page, a filled example, and an owner and review point.
Best for
Team leads, engineering managers, and ops people standardizing postmortems, design docs, decision records, bug reports, or meeting notes in Confluence and Jira.
SKILL.md preview
---
name: atlassian-templates
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Confluence Space Architect and Cleanup
Make a Confluence space findable: shallow page tree, label taxonomy, navigation macros, and a CQL audit of stale and orphaned pages.
Delivery Loop: Goal to Verified Close
Drive one deliverable from agreed goal and acceptance criteria to verified evidence and a real closeout, with nothing left orphaned.
Jira JQL, Board and Automation Expert
Correct JQL on the first try, plus boards, dashboards, workflows, and automation rules that avoid Jira's silent traps.
Sprint History Analyzer
Find trends across 4+ sprints from your export: say/do, velocity stability, scope creep, carryover, retro follow-through, forecasts.