skills.rest
hanh-nd
hanh-ndCOMMUNITY
Explore all skills by this author →
GitHub

ticket

Fetches a Jira ticket and routes it to the planning pipeline.

Updated Mar 24, 2026
Search Tags:#workflow#planning#fetch#handoff#jira#ticket#confluence
One-click install
npx skills add https://github.com/hanh-nd/agent-kit --skill ticket-hanh-nd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/hanh-nd/agent-kit/tree/main/plugins/agent-kit/.gemini/skills/ticket
Command: npx skills add https://github.com/hanh-nd/agent-kit --skill ticket-hanh-nd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually copying Jira ticket details into a planning workflow is repetitive and error-prone, especially when requirements are scattered across linked Confluence pages. This Skill fetches the ticket, gathers relevant context, and hands it off to planning in one step. ## Core Features & Use Cases - Ticket ID Extraction: Parses a ticket ID from raw input, whether it is a full Jira URL or embedded in free text. - Context Enrichment: Detects Confluence links in the ticket description and fetches pages likely to contain requirements or acceptance criteria. - Structured Handoff: Formats the ticket as a clean markdown brief, saves it via a handoff tool, and offers an interactive menu to start planning immediately. - Use Case: Paste a Jira URL like https://jira.com/browse/PROJ-123 and receive a saved ticket brief ready to feed directly into the planning skill. ## Quick Start Ask the agent to fetch Jira ticket PROJ-123 and prepare it for planning.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I fetch a Jira ticket from a URL?▼

Paste the full Jira URL or just the ticket ID as input. The skill extracts the ID (e.g., PROJ-123 from https://jira.com/browse/PROJ-123) and calls the Jira tool to retrieve the ticket details.

How to include Confluence requirements in a Jira ticket brief?▼

The skill scans the ticket description for Confluence links and fetches pages whose titles or context suggest requirements, acceptance criteria, or product specs. Remaining links are listed as references without being fetched.

Can I use this with tickets that have no Confluence links?▼

Yes. If the ticket description contains no Confluence links, the skill simply formats the ticket fields into a markdown brief and saves it without fetching any additional pages.

What happens after the ticket brief is saved?▼

An interactive menu appears offering to start the planning skill with the saved brief, finish with no further action, or enter a custom request to continue the conversation about the ticket.

Why is my ticket ID not being recognized?▼

The skill expects a recognizable ticket key pattern such as PROJ-123, either standalone, inside a URL, or within surrounding text. Input without a valid project-key-number pattern cannot be routed to the Jira tool.

Related Skills

Explore More Software Engineering Skills→
walconwalcon

atlassian

Perform CRUD operations on Jira issues and Confluence pages via REST APIs.

Community
Advanced
warpcodewarpcode
2

pm-task-analyser

Analyze software tickets to produce technical briefs, effort estimates, and implementation checklists.

Community
Advanced
christian-byrnechristian-byrne

slack-context-fetcher

Fetch Slack thread content via slackdump CLI for ticket context enrichment.

Community
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:gh-pr-create

Automate GitHub pull request creation with ticket extraction and Job Story summaries.

Official
Advanced