jira-fetch

Fetch Jira Epics and assemble subtasks into a prioritized Task Queue.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill jira-fetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-fetch
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/jira-fetch
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill jira-fetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira Epics often contain multiple subtasks and context fragmentation; this skill fetches Epics and assembles a prioritized Task Queue while loading the work context for downstream automation.

Core Features & Use Cases

  • Fetch Jira Epics and their subtasks to form a ready-to-execute Task Queue.
  • Load and cache task context for automation workflows.
  • Use Case: A sprint planning session where Epics are converted into ordered tasks with status and story points for deployment.

Quick Start

Fetch the Jira Epic and assemble its subtasks into a prioritized Task Queue with loaded context.

Frequently Asked Questions about jira-fetch

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

FAQPage Schema
How do I extract Jira subtasks from Epics into a task queue?

You can extract Jira subtasks from Epics by fetching the parent Epics and assembling their child issues into a prioritized, ready-to-execute task queue. This skill automates querying Epics and structuring subtasks for downstream workflows.

What is the best way to load work context for Jira task automation?

Loading work context for Jira task automation involves fetching Epic subtasks and caching their contextual data. This approach ensures downstream agents receive prioritized tasks with pre-loaded context, reducing fragmentation during sprint execution.

Can I use this approach for sprint planning with Jira Epics?

Yes, this approach supports sprint planning by converting Jira Epics into ordered tasks. It computes priorities and loads per-task context, allowing teams to deploy structured work items with status and story points directly into their sprints.

Does this Jira task queue approach handle backlog grooming?

This approach handles backlog grooming by fetching Jira Epics and assembling their subtasks into an ordered task queue. It extracts subtasks and computes priorities, streamlining the backlog refinement process for Jira-driven workflows.

How do I compute priorities for Jira subtasks extracted from Epics?

Computing priorities for Jira subtasks involves fetching parent Epics and evaluating their child issues to form a structured task queue. The skill automatically calculates subtask priorities to ensure ordered execution for downstream automation agents.

What are the limitations of automating Jira Epic subtask extraction?

Automating Jira Epic subtask extraction focuses specifically on querying Epics and assembling their child issues. It addresses context fragmentation but does not execute the tasks directly, serving purely to load context and compute priorities for downstream agents.