generic-jira-contributor-context

Aggregates a Jira contributor's identity, team, sprint, and ticket statuses via Atlassian MCP tools.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-jira-contributor-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generic-jira-contributor-context
Source: https://github.com/Puzzle9900/puzzle9900-claude-plugin/tree/main/skills/generic-jira-contributor-context
Command: npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-jira-contributor-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive snapshot of a Jira contributor's current workload, including their identity, team, active sprint details, and a breakdown of their assigned tickets by status.

Core Features & Use Cases

  • Contributor Identification: Resolves a contributor's account details, defaulting to the authenticated user.
  • Active Sprint Details: Dynamically identifies the active sprint, its name, dates, goal, and associated board.
  • Ticket Status Breakdown: Aggregates and counts all tickets assigned to the contributor within the active sprint, categorized by their status.
  • Use Case: A project manager can use this Skill to quickly understand a developer's current focus, identify potential bottlenecks by looking at ticket statuses, and get a clear overview of their sprint progress without manually navigating Jira.

Quick Start

Use the generic Jira contributor context skill to pull the full Jira context for the authenticated user.

Frequently Asked Questions about generic-jira-contributor-context

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

FAQPage Schema
How do I get a Jira contributor's sprint workload and ticket status breakdown?

You can aggregate a Jira contributor's sprint workload by resolving their identity, active sprint details, and assigned ticket status breakdown using Atlassian MCP tools. This provides a structured snapshot of their current sprint progress and potential bottlenecks.

What is included in a Jira contributor's active sprint context?

Jira contributor context includes the user's account identity, team affiliation, active sprint name, dates, goal, associated board, and a categorized count of all assigned tickets broken down by their current status.

Can I default Jira ticket aggregation to the authenticated user if no contributor is specified?

Yes, Jira context aggregation supports default user resolution. If no specific contributor is provided, the skill automatically resolves and fetches the workload context for the authenticated user.

How do I resolve team affiliation and active sprint details dynamically in Jira?

You dynamically resolve Jira team context and active sprint information by using Atlassian MCP tools. This identifies the active sprint's name, dates, goal, and associated board without manual navigation.

Does Jira contributor context aggregation handle contributor disambiguation?

Yes, the aggregation process handles contributor disambiguation to accurately resolve account details. It ensures the correct Jira user identity is targeted before pulling their sprint and ticket data.