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

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

Step 1: Fetch Ticket

Execute fetch script:

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:

## Jira Ticket: {key}

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

**Description:**
{description}

Step 3: Trigger PRD Skill

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

1. Inform the user: Briefly state that you’re now creating a PRD based on the ticket
2. Provide context: The PRD skill has access to the ticket details from Step 2
3. 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:

1. Runs python3 scripts/fetch_jira_ticket.py JIRA-123
2. Displays ticket info (link, title, description)
3. Says: “Now creating a PRD based on this ticket. I have the ticket context and will ask clarifying questions.”
4. 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”