How to use the Jira Project Management Expert agent skill

What the jira skill makes the agent do

An agent skill is a folder containing instruction text that the agent reads when a task matches it. This skill's only file is SKILL.md. Once it is active, the agent works as a Jira specialist: it structures work as Epics, Stories, Tasks and Sub-tasks, and it writes issue titles that describe an outcome rather than an activity.

The skill also gives the agent a set of practices for backlogs, sprint sizing, workflow setup and Jira's search language, JQL, including ready-made query patterns.

• Structure work as Epic > Story > Task > Sub-task
• Write outcome-focused titles and issues with acceptance criteria, priority and assignee
• Size sprints from team velocity and aim for about 80% capacity
• Write JQL for filtering and reports
• Suggest simple workflow states and board column setups

Install the jira skill from the ZIP

Download the ZIP for the jira skill from this page. Unzip it so that the jira folder, containing SKILL.md, sits in one of the following locations.

For a personal skill available in all your projects, place it in ~/.claude/skills/. For a skill that only applies to one project, place it in that project's .claude/skills/ folder.

You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/jira/
• Project only: .claude/skills/jira/ inside your project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Trigger the skill with natural requests

You do not need a special command. Ask for Jira help in plain language and mention Jira, so the agent recognises the task. Requests such as help with sprint planning, how do I write a good Jira story, or write a JQL query for open bugs fit the skill's purpose.

Be specific about your situation. Telling the agent your team size, sprint length and what you want to find or plan gives more useful answers than a general question.

• "Help me break this feature into a Jira Epic with Stories and Sub-tasks."
• "Rewrite this ticket title so it describes the outcome."
• "Write JQL to find stale issues not updated in 30 days."
• "Plan a sprint for a team with a velocity of about 40 points."

Examples of queries the skill covers

The skill includes example JQL patterns you can adapt. Replace the sample names, such as Sprint 23 or the engineering group, with your own before running them in Jira.

• Open bugs assigned to you: type = Bug AND assignee = currentUser() AND status != Done
• Sprint scope: sprint = "Sprint 23" ORDER BY priority DESC
• Stale issues: updated <= -30d AND status != Done
• Blockers: priority = Highest AND status != Done AND issueLinkType = "is blocked by"
• Team workload: assignee in membersOf("engineering") AND sprint in openSprints()

What you need and what the skill cannot do

The skill is guidance only. It does not connect to your Jira account and it does not create, edit or read live issues. To have the agent act on real data, you need a separate Jira tool, which is not included here. A Jira Cloud or Jira Data Center account is only needed in that case.

The advice is generic. If your organisation has fixed sprint lengths or its own workflow states, adapt the suggestions rather than following them literally. The skill runs no scripts and uses no network access.

• Runs scripts: no
• Uses network: no
• Jira account: only needed if you pair the skill with a separate Jira tool

Safety notes on scripts and network

According to the skill's own description, it runs no scripts and makes no network requests. It is instruction text, so reviewing SKILL.md tells you exactly what guidance the agent receives. Check any JQL or workflow change against your own Jira instance before applying it to live projects.

• Review SKILL.md before installing if you want to see every instruction
• Test JQL in a non-production filter first
• Confirm workflow and board changes with your Jira administrator

Tips for getting better results

Give the agent the context a teammate would need. The skill itself warns against issues like Fix the bug, which are not actionable. Paste your current ticket or backlog excerpt and ask for a rewrite.

Keep discussion out of Jira where possible. The skill suggests putting conversations in comments or linked chat threads, and keeping custom fields to a minimum.

• Paste real ticket text and ask for a rewrite against acceptance criteria
• Ask for simpler workflows before adding states
• Ask why a recommendation fits your team before adopting it