jira

Route natural language Jira requests to CLI or MCP backends.

40|4|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/jjmartres/ai-coding-agents --skill jira-jjmartres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/jjmartres/ai-coding-agents/tree/main/shared/.ai-agents/skills/jira
Command: npx skills add https://github.com/jjmartres/ai-coding-agents --skill jira-jjmartres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Natural language Jira management that routes queries to the correct backend (CLI or MCP) and provides guided actions for issue tracking.

Core Features & Use Cases

  • Backend auto-detection: CLI when jira is available, otherwise MCP for Atlassian Jira.
  • End-to-end Jira workflows: view, create, edit issues; manage sprints and transitions; add comments; and project/list metadata.
  • Reference and safety: inline references and prompts for confirmation before destructive actions.

Quick Start

Describe your Jira task and I will perform the action using the available Jira backend.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I manage Jira issues using natural language?

You can manage Jira issues by describing your task in natural language, which routes requests to the correct Jira backend. The system auto-detects whether to use the Jira CLI or MCP to execute actions like viewing, creating, and updating tickets.

Can I create and update Jira tickets through an automated workflow?

Yes, you can automate Jira workflows to create and update issues, manage sprint transitions, and add comments. The system detects your available Jira interfaces and executes the requested ticket actions directly.

Do I need the Jira CLI installed to manage issues and sprints?

No, you do not need the Jira CLI installed to manage issues and sprints. The system auto-detects your backend, defaulting to the CLI if available, and otherwise falling back to MCP for Atlassian Jira integration.

How does backend detection work for Jira ticket automation?

Backend detection for Jira ticket automation checks for local jira CLI availability. If the CLI is present, it routes requests there; otherwise, it defaults to MCP for Atlassian Jira to execute your issue management tasks.

Are there safeguards against destructive actions when updating Jira issues?

Yes, safeguards are implemented against destructive actions when updating Jira issues. The system prompts for explicit user confirmation before executing sensitive modifications, ensuring safe backlog and ticket management.

What should I do if my Jira sprint management request fails?

If your Jira sprint management request fails, review the clear error messages provided by the backend. Ensure you have valid Jira access, correct project metadata, and that your CLI or MCP backend is properly configured.