skills.rest
lukeylias
lukeyliasCOMMUNITY
Explore all skills by this author →
GitHub

jira

Convert resolved conversation context into a structured Jira ticket.

Updated Apr 25, 2026
Search Tags:#requirements#product management#acceptance criteria#issue tracking#jira#ticket
One-click install
npx skills add https://github.com/lukeylias/lukeydev --skill jira-lukeylias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/lukeylias/lukeydev/tree/main/skills/jira
Command: npx skills add https://github.com/lukeylias/lukeydev --skill jira-lukeylias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns already resolved conversation context into a clear, copy-paste-ready Jira ticket, saving time and reducing the risk of losing important decisions in informal chat.

Core Features & Use Cases

  • Structured Ticket Drafting: Produces a concise title, a short description, and acceptance criteria in a format teams can paste directly into Jira.
  • Scope Checking: Detects when a discussion covers more than one piece of work and asks for a single ticket focus before proceeding.
  • Decision Synthesis: Reuses agreed details from prior discussion instead of re-interviewing the user, making it ideal after a planning or shaping conversation.

Quick Start

Use the jira skill to turn the resolved discussion about the checkout error into a Jira ticket.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I create a Jira ticket from a resolved conversation without re-entering all the details?▼

This Skill synthesises resolved conversation context into a structured Jira ticket, producing three copyable blocks for title, description, and acceptance criteria that are ready to paste directly into your issue tracker.

What is the best way to generate acceptance criteria from a planning discussion?▼

Generating acceptance criteria from a planning discussion reuses the agreed details from your prior conversation. It formats the output in testable language using UK English, ensuring the criteria are concise and ready for formal issue tracking.

How do I draft a concise Jira ticket title when the discussion covers multiple features?▼

Drafting a concise Jira ticket title requires a single ticket focus. The Skill detects when a discussion covers more than one piece of work and asks you to narrow the scope before proceeding with title generation and description synthesis.

Can I turn product management decisions into issue tracking tickets without manual formatting?▼

Turning product management decisions into issue tracking tickets is handled automatically. The Skill takes post-decision context and applies scope checking, concise title generation, and structured formatting to output a ready-to-use issue.

When do I need to use a conversation synthesis tool for ticket creation?▼

You need a conversation synthesis tool for ticket creation when you have finished a planning or shaping conversation and need a formal issue. It applies to post-decision ticket creation for a single piece of work from an existing discussion.

Related Skills

Explore More Product & Management Skills→
fartybobofartybobo
4

create-jira-ticket

Create Jira tickets from conversation and code context in Atlassian Document Format.

Official
Advanced
valec3valec3
1

jira-task

Create Jira tasks with standardized titles, descriptions, acceptance criteria, and references.

Community
Basic
SkogAISkogAI
1

brainstorming

Refine rough ideas into concrete designs through collaborative questioning.

Official
Basic
buihuulocbuihuuloc

github-create-issue

Create GitHub issues from git history with titles, descriptions, and acceptance criteria.

Community
Advanced