jira

Translate natural language into Jira view, create, update, and transition commands.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/gabi-agent/openretro --skill jira-gabi-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/gabi-agent/openretro/tree/main/skills/jira
Command: npx skills add https://github.com/gabi-agent/openretro --skill jira-gabi-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jira is a central hub for issue tracking in software projects, and many teams interact with it through manual commands or web UIs. This skill provides a natural language interface to view, create, update, and manage Jira tickets, bridging the gap between human intent and Jira operations.

Core Features & Use Cases

  • Conversational access to view, list, create, update, and transition Jira issues across projects.
  • Sprint and backlog management, including querying current sprint status and adding/removing issues.
  • Backed by either a Jira CLI or Atlassian MCP, with safety checks, current-state fetch before modifications, and explicit user approvals for changes.

Quick Start

Ask Jira to view an issue such as PROJ-123, or request the creation of a new ticket with a concise summary and description.

Frequently Asked Questions about jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and update Jira issues using natural language?

This skill automates Jira issue management by translating natural language conversations into view, create, update, and transition commands. It supports both Jira CLI and Atlassian MCP backends to execute operations.

Can I manage Jira sprints and backlog tickets without using the web UI?

Yes, you can manage Jira sprints without the web UI. The skill supports querying current sprint status and adding or removing issues from sprints through conversational requests.

Does this Jira automation skill require a specific backend like CLI or MCP?

The skill requires either a Jira CLI or Atlassian MCP backend to be available. It uses these backends to execute operations and can optionally look up account IDs for MCP integrations.

How are Jira ticket modifications safeguarded during conversational automation?

Modifications are safeguarded by fetching real-time state before applying changes and requiring explicit user approval. This ensures no Jira issues are created, updated, or transitioned without confirmation.

What is the best way to transition Jira issues across projects automatically?

The best way to transition issues automatically is through conversational commands translated into Jira backend operations. The skill applies transitions across projects after fetching real-time state and securing user approval.