jira-fetcher

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Fetch Jira ticket details from Jira Cloud and prepare for PRD planning. Use when user asks to fetch, load, or work on a Jira issue (e.g., 'Fetch JIRA-123', 'Load issue XYZ-456', 'I'm working on ticket ABC', 'Get details for PROJ-789'). This skill retrieves ticket link, ID, title, and description, then triggers PRD skill to create an implementation plan based on the ticket context.

1installs

Sourcewireless25/agentic-coding

Added on2026-02-09

NPX Install

npx skill4agent add wireless25/agentic-coding jira-fetcher

SKILL.md Content

View Translation Comparison →

Jira Ticket Fetcher

Fetch Jira ticket details and trigger PRD planning workflow.

Prerequisites

Set these environment variables:

```
JIRA_API_TOKEN
```
: Personal access token for Jira Cloud authentication
```
JIRA_EMAIL
```
: Your Atlassian account email address

JIRA_SITE_URL

: Jira site URL (default:

https://sozialinfo.atlassian.net

)

Workflow

Fetch ticket: Run fetch script with the ticket key
Display ticket info: Show link, ticket ID, title, and description
Trigger PRD skill: Immediately start PRD planning with ticket context

Step 1: Fetch Ticket

Execute fetch script:

bash

python3 scripts/fetch_jira_ticket.py <ticket-key>

The script returns JSON with:

```
key
```
: Ticket ID (e.g., "PROJ-123")
```
link
```
: Direct URL to the ticket
```
title
```
: Ticket summary/title
```
description
```
: Ticket description (may be in Atlassian Document Format)

Handle errors by returning the full API error message to the user.

Step 2: Display Ticket Info

Present the fetched information to the user in a clear format:

markdown

## Jira Ticket: {key}

**Link:** {link}
**Title:** {title}

**Description:**
{description}

Step 3: Trigger PRD Skill

After displaying the ticket, immediately start the PRD planning workflow:

Inform the user: Briefly state that you're now creating a PRD based on the ticket
Provide context: The PRD skill has access to the ticket details from Step 2
Ask clarifying questions: Use the PRD skill's question format with ticket context in mind

Example PRD question:

Based on this ticket, what is the primary goal?
A. [Option based on ticket]
B. [Option based on ticket]
C. [Option based on ticket]
D. Other: [please specify]

The PRD skill will then generate a comprehensive PRD document with:

User stories and acceptance criteria
Functional requirements
Success metrics
Non-goals (out of scope)

Important Notes

No automatic PRD creation: Do NOT create the PRD automatically. Let the PRD skill handle its workflow (questions → generation)
Context availability: The PRD skill has full ticket context available when asking clarifying questions
Error handling: If the API call fails, return the exact error message from the API response
Description format: Jira descriptions may be in Atlassian Document Format (JSON); present this to the user as-is

Example Session

User: "Fetch JIRA-123"

Agent:

Runs

python3 scripts/fetch_jira_ticket.py JIRA-123

Displays ticket info (link, title, description)
Says: "Now creating a PRD based on this ticket. I have the ticket context and will ask clarifying questions."
Activates PRD skill and asks: "Based on this ticket about user authentication, what's the primary goal? A. Improve security, B. Simplify login, C. Add OAuth, D. Other"