jira

Generate JIRA tickets with summaries and markdown descriptions from short user descriptions.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/BrianProcopio/claude-skills --skill jira-brianprocopio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/BrianProcopio/claude-skills/tree/main/jira
Command: npx skills add https://github.com/BrianProcopio/claude-skills --skill jira-brianprocopio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of JIRA tickets by transforming brief user requests into well-formatted, actionable tickets optimized for both human review and AI-driven task planning.

Core Features & Use Cases

  • Automated Ticket Generation: Creates JIRA tickets (Stories, Bugs, Tasks, Epics) from short descriptions.
  • Structured Output: Produces a concise summary and a detailed description with Context, Requirements, Acceptance Criteria, and Technical Notes.
  • Use Case: When you need to quickly document a new feature request or a bug, use this Skill to generate a complete JIRA ticket that clearly outlines the work needed.

Quick Start

Use the jira skill to write a ticket for adding a user profile page.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I generate a structured JIRA ticket from a short description?

To generate a JIRA ticket, input a brief description of your request. The tool structures it into a concise summary and a detailed markdown description including Context, Requirements, and Acceptance Criteria.

What is the best way to write JIRA bug reports and stories for AI task consumption?

The best way to write JIRA bug reports and stories for AI task consumption is to use structured markdown. This tool formats your short descriptions into detailed tickets with specific sections optimized for both human review and AI-driven planning.

Can I create different types of JIRA tickets like Epics and Tasks with this approach?

Yes, you can create different types of JIRA tickets. This approach supports generating Epics, Tasks, Stories, and Bug reports by applying specific guidance on crafting effective summaries and detailed descriptions for each type.

Do I need to provide full acceptance criteria to document a new feature request?

No, you do not need to provide full acceptance criteria to document a new feature request. You only need to provide a short user description; the tool automatically generates the acceptance criteria and technical notes for the JIRA ticket.

How does automated ticket generation handle technical notes and requirements?

Automated ticket generation handles technical notes and requirements by expanding a brief user request into a structured markdown format. It isolates specific technical requirements and notes to ensure the JIRA ticket clearly outlines the necessary work.

Are there limitations when transforming brief requests into JIRA stories?

A limitation when transforming brief requests into JIRA stories is that the output quality depends on the initial input clarity. While the tool structures the ticket, highly ambiguous short descriptions may result in generic requirements or technical notes.