Generate Jira ticket descriptions and acceptance criteria in Markdown.
npx skills add https://github.com/bkircher/skills --skill jira-write-ticket
Please help me install this Agent Skill. Skill: jira-write-ticket Source: https://github.com/bkircher/skills/tree/main/jira-write-ticket Command: npx skills add https://github.com/bkircher/skills --skill jira-write-ticket
This Skill streamlines the creation of Jira tickets by ensuring all necessary information is present and well-formatted, reducing back-and-forth for clarifications.
jira-read-ticket to include summaries of linked tickets.Use the jira-write-ticket skill to draft a new Jira ticket for the bug described in the provided context.
High-intent search queries and answers about installing and using this skill.
To write a Jira ticket with clear acceptance criteria, you need a structured Markdown template that separates the description, links, and acceptance criteria sections. This ensures all necessary information is present and well-formatted, reducing clarification requests.
The best way to format bug tracking tickets is using a standardized Markdown format that prompts for missing details. This approach identifies gaps in your ticket description and asks targeted questions to ensure complete documentation before submission.
Yes, you can link GitHub code references in Jira ticket documentation. The process converts standard code locations into GitHub permalinks, providing better context for developers directly within the ticket's Links section.
To include summaries of referenced Jira tickets during new ticket creation, the process integrates with a ticket reading skill that extracts and summarizes linked ticket information. This provides immediate context within your new ticket's Links section.
Yes, Markdown is required to create Jira tickets with this approach. The output strictly adheres to a predefined Markdown template containing Description, Links, and Acceptance Criteria sections, ensuring consistent formatting across all generated tickets.
When your Jira ticket description is missing required details, the system identifies the gaps and prompts you with targeted clarification questions. This ensures all necessary information is collected and clearly articulated before finalizing the ticket.
HaywardMoriharaCreate structured software tickets from brief problem descriptions.
jayleekrAutomate JIRA ticket workflows from analysis to pull request creation.
randalmurphalPerform Jira ticket operations with lightweight bash scripts.
abrahamgreysonGenerate detailed execution plans from wave descriptions and acceptance criteria.