skills.rest
OktayCopurlu
OktayCopurluCOMMUNITY
Explore all skills by this author →
GitHub

jira-ticket

Write, review, and improve Jira ticket content with testable acceptance criteria.

3|Updated Apr 2, 2026
Search Tags:#requirements#acceptance criteria#agile#jira#atlassian#ticket review#ticket writing
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill jira-ticket-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-ticket
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/jira-ticket
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill jira-ticket-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague, overly broad, or implementation-heavy Jira tickets slow down engineering execution and cause rework. This Skill produces clear, execution-ready ticket content with observable acceptance criteria and pushes back on weak or ambiguous requirements. ## Core Features & Use Cases - Ticket Writing: Drafts Jira tickets using a Context, Acceptance Criteria, Dev Note structure with testable, implementation-free acceptance criteria. - Ticket Review: Returns a structured verdict (Ready / Almost ready / Not ready) with blocking issues, non-blocking improvements, and suggested rewrites. - Ticket Updates: Preserves confirmed intent, updates only needed sections, and flags conflicts or missing information. - Use Case: Paste a rough feature idea like "add low stock warning on PDP" and receive a complete Jira-ready ticket with a clear title, context, 4-7 testable acceptance criteria, and a short Dev Note. ## Quick Start Ask the assistant to turn this feature idea into a Jira ticket with acceptance criteria.

Frequently Asked Questions about jira-ticket

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

FAQPage Schema
How do I write a good Jira ticket with acceptance criteria?▼

Structure the ticket as Context, Acceptance Criteria, and an optional Dev Note. Write acceptance criteria as observable outcomes using "When X, Y happens" phrasing, keeping 4-7 items for small tickets and avoiding implementation details like props, hooks, or store names.

How to review a Jira ticket before refinement?▼

Use the review mode to get a verdict of Ready, Almost ready, or Not ready, plus blocking issues, non-blocking improvements, missing information, and a suggested rewrite of the weakest sections. Vague or untestable criteria are flagged explicitly.

Can this skill create or update tickets in Jira directly?▼

No, it handles ticket content quality only, not CRUD operations. For creating, searching, or transitioning Jira issues, use the atlassian-mcp skill; this skill can fetch existing tickets via the Atlassian MCP server for review or rewriting.

What should acceptance criteria in a Jira ticket avoid?▼

Acceptance criteria must avoid implementation details such as component APIs, props, hooks, store names, and data structures. They should also exclude engineering standards like unit tests or responsiveness, describing only outcomes QA, PM, or design can verify.

When should a Jira ticket be split into multiple tickets?▼

Split a ticket when it mixes unrelated surfaces, combines discovery with implementation, spans multiple teams or dependencies, or has acceptance criteria covering several independent deliverables. The skill suggests splitting when these conditions appear.

Related Skills

Explore More Product & Management Skills→
STUkhSTUkh
27

sparq:analyze

Consolidate project requirements from Jira, Confluence, Figma, and local files into a unified spec.

Community
Intermediate
mParticlemParticle
7

implement-ticket

Automate Jira ticket implementation into a feature branch and GitHub pull request.

Official
Advanced
danhannah94danhannah94

csdlc-doc

Generate Step 0 design docs for projects, epics, or subsystems using bundled templates.

Community
Intermediate
fabiano001fabiano001

ticket-creator

Generate structured Jira tickets with acceptance criteria from brief descriptions.

Community
Advanced