jira-assistant_skill

Overview

This skill is a JIRA automation hub that routes user requests to one of 13 specialized JIRA skills. It does not perform JIRA operations directly; it chooses the correct skill for issue CRUD, workflows, agile tasks, searches, time tracking, service management, admin work, and bulk actions. The hub enforces safety rules, clarifies ambiguous requests, and tracks short-term context to improve routing accuracy.

How this skill works

The hub analyzes user intent, keywords, entity signals (like issue keys), and item counts to pick the most appropriate downstream skill. It follows explicit routing rules, negative triggers, and a disambiguation table to avoid incorrect routing. For potentially destructive operations it asks clarifying questions and requires confirmation before delegating to high‑risk skills.

When to use it

• You want help finding which JIRA skill should handle a request rather than executing the action directly.
• You need routing for single-issue CRUD, transitions, or comments and want the correct specialized skill recommended.
• You have a search, JQL, or bulk workflow and want guidance on whether to use search, bulk, or agile skills.
• You need safe handling of destructive or high-risk tasks and want confirmation and dry-run behavior enforced.
• You want a quick view of available JIRA capabilities or a skills index before running operations.

Best practices

• Mention explicit skill names when you want a specific handler (e.g., "use jira-agile").
• Include issue keys or counts where possible to improve automated routing (single issue vs bulk).
• Expect clarification when a request matches multiple skills or implies destructive actions.
• Confirm before executing high-risk workflows; use dry-run for bulk operations (50+ issues).
• Keep project context explicit when it changes; the hub remembers recent project scope but re-confirms after context expires.

Example use cases

• "Show me TES-123" → routes to jira-issue for a single issue lookup and display.
• "Find all open P1 bugs and close them" → uses jira-search to find results, then jira-bulk with a dry-run and confirmation.
• "Create an epic and add stories" → routes epic creation to jira-agile, then creates stories with jira-issue or links them via jira-agile.
• "List SLA queues for service desk" → routes to jira-jsm to inspect queues, SLAs, and request types.
• "Warm project cache or run diagnostics" → routes to jira-ops for discovery, caching, and diagnostics.