jira-management

Manage Jira boards and issues with Atlassian Rovo MCP conventions.

59|12|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill jira-management-etylsarin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-management
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/plugins/jira
Command: npx skills add https://github.com/etylsarin/opencastle --skill jira-management-etylsarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reproducible Jira convention and MCP integration to ensure feature work is decomposed, tracked, and resumed consistently across multi-agent teams.

Core Features & Use Cases

  • Conventions: standardized issue naming, labels, priority mapping, status workflow, epic grouping, and files (partition) guidance to avoid merge conflicts during parallel work.
  • MCP Integration: guidance for searching with JQL, creating and updating issues, reading comments and attachments, and retrieving Confluence context via the Atlassian Rovo MCP.
  • Session Continuity: procedures to resume interrupted sessions by locating In Progress and To Do issues and restoring agent context.
  • Use Case: decompose a new feature into an Epic and a set of linked issues, assign Files partitions to each issue, create the Jira issues via MCP, then delegate work to agents.

Quick Start

Ask the team-lead agent to decompose the feature into Jira issues using the jira-management conventions and create the Epic plus linked tasks with correct naming, priorities, and Files partitions.

Frequently Asked Questions about jira-management

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

FAQPage Schema
How do I standardize Jira issue naming and priority mapping for multi-agent feature tracking?

You standardize Jira workflows by applying predefined conventions for issue naming, labels, priority mapping, and status transitions, ensuring consistent feature tracking across multi-agent teams using the Atlassian Rovo MCP.

How do I decompose a Jira Epic into linked issues using JQL and MCP integration?

You decompose a feature by creating an Epic and linked issues via the Atlassian Rovo MCP, assigning Files partitions to each task to avoid merge conflicts, and using JQL to search and manage the resulting issues.

Does Jira MCP integration support retrieving Confluence context for feature decomposition?

Yes, the Atlassian Rovo MCP integration supports retrieving Confluence context to inform feature decomposition, alongside searching with JQL, creating issues, reading comments, and linking pull requests.

How do I resume interrupted Jira agent sessions using issue status workflows?

You resume interrupted agent sessions by using JQL to locate In Progress and To Do issues, restoring the agent context from the standardized Jira workflow status and Files partition assignments.

What's the best way to avoid merge conflicts when parallel agents work on Jira issues?

The best way to avoid merge conflicts during parallel work is to assign Files partitions to each Jira issue, a convention enforced by the jira-management workflow to separate file ownership across agents.

Can I link pull requests to Jira issues using the Atlassian Rovo MCP?

Yes, you can link pull requests to Jira issues using the Atlassian Rovo MCP, which integrates issue creation, updates, and workflow transitions to maintain traceability across feature development.