skills.rest
hoshiyar-singh8
hoshiyar-singh8COMMUNITY
Explore all skills by this author →
GitHub

jira-ticket-standard

Standardize Jira ticket content with required sections and API payload patterns.

Updated Mar 16, 2026
Search Tags:#template#review#jira#ticket#acceptance-criteria#standard
One-click install
npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill jira-ticket-standard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-ticket-standard
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/jira-ticket-standard
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill jira-ticket-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides background knowledge and a standardized framework for creating Jira tickets, ensuring consistency, completeness, and alignment with HeroGen workflows.

Core Features & Use Cases

  • Establishes a consistent ticket structure (summary, description, acceptance criteria, references) and a predictable Jira API payload pattern
  • Defines best practices and reference patterns to guide reviewers and ensure tickets are actionable
  • Offers common use cases such as creating new product tickets, updating existing issues, and enforcing cross-platform consistency

Quick Start

Create a Jira ticket following the Jira Ticket Standard template described above.

Frequently Asked Questions about jira-ticket-standard

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

FAQPage Schema
How do I standardize Jira tickets for consistency and completeness?▼

Standardizing Jira tickets requires applying a fixed task template with required sections: summary, description, explicit acceptance criteria, and references. This ensures consistent formatting and actionable content across iOS, Android, and backend project workflows.

What should be included in Jira ticket acceptance criteria for backend and mobile projects?▼

Jira ticket acceptance criteria must be explicit and accompanied by defined reference patterns. The standard enforces a consistent ticket structure that covers formatting, required sections, and API payload expectations across iOS, Android, and backend projects.

Does the Jira ticket standard support cross-platform workflows like iOS and Android?▼

Yes, the Jira ticket standard applies to HeroGen ticket workflows across iOS, Android, and backend projects. It enforces cross-platform consistency by defining required ticket sections and predictable API payload expectations.

What is the best way to format Jira API payloads when creating new product tickets?▼

The best way to format Jira API payloads is to follow the standardized reference patterns defined for the HeroGen workflow. This ensures the payload meets the fixed task template requirements and explicit acceptance criteria before submission.

When do I need to use a fixed Jira ticket template for issue review?▼

You need a fixed Jira ticket template during issue review to guarantee the ticket contains required sections, explicit acceptance criteria, and reference patterns. This framework guides reviewers by ensuring all tickets are complete and actionable.

Related Skills

Explore More Product & Management Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
garethrhughesgarethrhughes
5

jira-feature

Fetch Jira tickets and convert them into feature briefs.

Community
Advanced
aaronbassettaaronbassett
4

flutter-core:flutter-deployment

Automate Flutter deployment guidance across Android, iOS, Web, and Desktop.

Community
Advanced
markus41markus41
1

jira

Automates Jira project management including issues, sprints, and workflows via API.

Community
Intermediate