jira-tools

This skill MUST be used when the user asks to "analyze backlog issues", "analyze backlog", "analyze top backlog items", "Claude analyze tickets", "run analysis on backlog", "AI analyze Jira issues", "bulk analyze issues", "analyze unanalyzed tickets", or wants to have Claude automatically analyze and annotate multiple backlog issues. This skill finds the top 3 backlog issues without the claude-analyzed label, performs issue-analysis on each, and updates the Jira description with a Claude Analysis section.

This skill MUST be used when the user asks to "get backlog", "list backlog issues", "show backlog", "what's in the backlog", "backlog summary", "list Jira issues", "show issues in project", "what issues are pending", "show sprint issues", "active sprint", "past sprints", or needs a quick overview of multiple issues. Use this for bulk issue listing - use jira-issue for single issue details.

This skill MUST be used instead of Atlassian MCP tools when the user asks to "create a Jira issue", "create a ticket", "add a Jira ticket", "make a new issue", "file a bug", "create a story", "add a task in Jira", or otherwise requests creating new Jira issues. ALWAYS use this skill for Jira issue creation - never use mcp__atlassian__createJiraIssue directly.

This skill MUST be used when the user asks to "analyze issue", "plan implementation", "how to fix issue", "create plan for ticket", "what's needed for this issue", "implementation strategy", "analyze Jira ticket", "plan for PROJ-123", or wants to understand how to implement a Jira issue in their codebase. Use this skill to create actionable implementation plans.

This skill MUST be used when the user asks to summarize their own Jira activity, what they personally worked on, or what they did in Jira over a time period. Trigger phrases include "summarize my jira activity", "what did I do in jira", "show my jira activity", "my activity in mbc", "what did I work on", "jira activity report", or any request combining a personal possessive ("my") with a Jira project and a time period (today, yesterday, this week, last week, this month). This skill is specifically for personal activity summaries — NOT sprint reports, NOT backlog listings, NOT issue searches. Examples: "summarize my jira activity in mbc yesterday", "what did I work on in mbc this week", "show my mbc activity last week".

This skill MUST be used instead of Atlassian MCP tools when the user asks to "get Jira issue", "fetch Jira ticket", "look up issue", "show me ticket", "what's the status of PROJ-123", "get issue details", "find Jira issue", or mentions a Jira issue key pattern like "PROJ-123", "ABC-456". ALWAYS use this skill for Jira issue retrieval - never use mcp__atlassian__getJiraIssue directly.

This skill MUST be used when the user asks to "link issues", "relate issues", "mark as duplicate", "blocks issue", "is blocked by", "create issue link", "connect issues", or otherwise requests creating relationships between Jira issues.

This skill MUST be used when the user asks to "log work", "log time", "add worklog", "track time", "record hours", "time tracking", "log 2 hours", or otherwise requests adding time entries to Jira issues.

This skill MUST be used when the user asks to "create sprint", "start sprint", "end sprint", "complete sprint", "close sprint", "new sprint", "begin sprint", "finish sprint", "update sprint", "rename sprint", or otherwise wants to create or change sprint state/details.

This skill MUST be used when the user asks to "move issue to sprint", "add to sprint", "assign to sprint", "put in sprint", "add issue to current sprint", "move to backlog", "remove from sprint", or otherwise wants to change which sprint an issue belongs to.

This skill MUST be used when the user asks to "search issues", "find issues", "JQL search", "query Jira", "list issues matching", "find tickets where", "search for bugs", "find my issues", or otherwise requests searching for Jira issues using criteria or JQL.

This skill MUST be used when the user asks to "get sprint info", "show sprint details", "what's in the sprint", "sprint status", "current sprint", "active sprint details", "list sprint issues", "sprint progress", or needs information about a specific sprint. Use this for sprint-level details - use backlog-summary for bulk issue listing across sprints.

This skill MUST be used when the user asks for "sprint report", "sprint summary", "sprint burndown", "sprint velocity", "sprint metrics", "how is the sprint going", "sprint health", "sprint completion", or needs a detailed analysis of sprint progress and performance.

This skill MUST be used instead of Atlassian MCP tools when the user asks to "update a Jira issue", "edit a ticket", "change issue status", "transition ticket", "assign issue", "add labels", "update priority", "add comment to ticket", "move issue to done", "close ticket", or otherwise requests modifying existing Jira issues. ALWAYS use this skill for Jira issue updates - never use mcp__atlassian__editJiraIssue or mcp__atlassian__transitionJiraIssue directly.

This skill MUST be used when the user asks to "watch issue", "add watcher", "remove watcher", "stop watching", "follow issue", "unfollow issue", "subscribe to issue", or otherwise requests managing watchers on Jira issues.