OpenParable
Skip to content
← Back to skills

Jira Expert

Productivity
jira-expert

Jira Expert is an Agent Skill for productivity published in the borghei/Claude-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Jira expert for project setup, workflow design, JQL queries, custom fields, automation rules, dashboards, and reporting. Use for Jira configuration, advanced search, board and dashboard creation, and technical Jira operations.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/borghei/Claude-Skills/blob/HEAD/project-management/jira-expert/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/jira-expert, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Atlassian Jira Expert

Master-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles all technical and operational aspects of Jira.

Core Capabilities

  • Project configuration — create Scrum/Kanban/custom projects, design custom workflows, configure issue types/fields/screens, set permission and security schemes
  • JQL mastery — author advanced queries, build complex filters, optimize query performance, create saved filters for teams
  • Automation & integration — design automation rules, configure webhooks and notifications, integrate Confluence/Slack/external tools
  • Reporting & dashboards — custom dashboards with gadgets, sprint/velocity/burndown reports, portfolio-level and executive reporting

When to Use

  • Setting up a new project and its workflow, fields, and board
  • Writing or debugging JQL for filters, reports, or dashboards
  • Designing automation rules and avoiding trigger loops
  • Building dashboards and configuring gadgets for a team or exec
  • Managing custom fields, issue links, security levels, or bulk operations

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/jira-playbook.md — full detail behind this map: competencies, workflows (project creation, workflow design, dashboards, automation), JQL operators/functions, advanced features (custom fields, linking, security, bulk ops), reporting templates, decision/handoff protocols, best practices, troubleshooting table, and success criteria. Read when executing any Jira task.
  • references/jql-examples.md — extended library of ready-to-run JQL queries grouped by use case (sprints, and more). Read when you need a specific query pattern fast.
  • references/automation-examples.md — concrete Jira automation rule recipes (auto-assignment, and more) with triggers/conditions/actions. Read when building or troubleshooting automation rules.
  • references/red-flags.md — common ways a Jira configuration, JQL query, automation rule, or dashboard goes wrong, with bad/good examples. Read before shipping any change to a team.

Scope & Limitations

In Scope: Jira project creation and configuration, workflow design and implementation, JQL query authoring and optimization, automation rule design, dashboard and reporting setup, custom field management, board configuration, bulk operations, issue linking strategies.

Out of Scope: Org-wide Atlassian administration (hand off to atlassian-admin/), Confluence space management (hand off to confluence-expert/), sprint execution and team coaching (hand off to scrum-master/), strategic project prioritization (hand off to senior-pm/).

Limitations: Jira Cloud automation has monthly execution limits per plan tier. Complex JQL on large instances (>100K issues) may hit performance ceilings. Workflow changes to active projects require careful migration planning -- retroactive changes do not apply to in-flight issues.

Integration Points

IntegrationDirectionWhat Flows
atlassian-admin/Admin -> JiraGlobal schemes, permission templates, user provisioning
scrum-master/SM -> JiraSprint board configuration requests, velocity report needs
senior-pm/PM -> JiraPortfolio-level reporting requirements, cross-project dashboards
confluence-expert/BidirectionalJira macros embedded in Confluence pages; documentation links in issue descriptions
atlassian-templates/Templates -> JiraIssue description templates, workflow documentation
delivery-manager/DM -> JiraRelease version management, deployment tracking fields