jira-fetcher_skill

Overview

This skill fetches Jira Cloud ticket details and prepares them for PRD planning. It retrieves the ticket link, ID, title, and raw description, then passes that context to the PRD workflow. Use it to quickly load an issue and start structured product planning without manual copying.

How this skill works

On request, the skill calls the Jira Cloud API with the provided ticket key and returns the ticket JSON containing key, link, title, and description. It presents the fetched fields clearly and then signals the PRD skill that ticket context is available for clarifying questions and PRD generation. If the API returns an error, the exact API error message is returned to the user.

When to use it

• When you ask to fetch or load a specific Jira issue (e.g., 'Fetch JIRA-123').
• Before starting PRD work to ensure the planning workflow has accurate ticket context.
• When you need the ticket URL, ID, title, and raw description quickly.
• When the ticket description may be in Atlassian Document Format and should be preserved as-is.

Best practices

• Provide the exact ticket key (project prefix and number) to avoid ambiguity.
• Ensure environment variables for Jira API credentials are set before invoking the skill.
• If the description is in Atlassian Document Format (ADF), treat it as source content and pass it unmodified to the PRD workflow.
• Do not expect the skill to auto-create a PRD; it only supplies context and triggers the PRD skill to run its question workflow.
• If an API error occurs, share the full error text with the user to aid troubleshooting.

Example use cases

• User: 'Fetch PROJ-789' — skill returns link, title, and description, then starts PRD questioning.
• User: 'Load issue ABC-456' — retrieve ticket JSON so product team can begin planning.
• Preparing for a planning meeting where you need canonical ticket details shared with the PRD generator.
• Handling tickets whose descriptions are in ADF so the PRD skill can interpret the original structure.