jira-tickets
Use when functional requirements are ready and approved. Creates JIRA Epics and Stories for EA then GA sequentially using JIRA MCP.
84
76%
Does it follow best practices?
Impact
96%
2.90xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/jira-tickets/SKILL.mdEvaluation results
100%
93%JIRA Ticket Plan: Real-Time Notification Service EA
Epic and Story format compliance
Epic summary EA prefix
0%
100%
Epic full feature name
100%
100%
Epic Resources section
0%
100%
Story summary bracket format
0%
100%
API work-type suffix
0%
100%
UI work-type suffix
0%
100%
DB work-type suffix
0%
100%
OPS work-type suffix
0%
100%
End Goal section
0%
100%
Implementation Details section
25%
100%
Estimate comment
0%
100%
Out of Scope section
0%
100%
90%
62%Sprint Ticket Breakdown: SSO Authentication EA
Story sizing and EA blocker handling
Large task split
100%
100%
Small tasks combined
0%
33%
Estimate per story
0%
100%
EA blocker note
0%
100%
Split story summaries
26%
100%
Epic summary format
26%
100%
100%
36%Two-Phase Ticket Plan: Data Ingestion Pipeline
Sequential EA then GA milestone processing
EA section before GA
100%
100%
EA Epic prefix
0%
100%
GA Epic prefix
0%
100%
Two separate Epics
100%
100%
Full feature name in both Epics
100%
100%
EA stories linked to EA Epic
100%
100%
GA stories linked to GA Epic
100%
100%
Consistent project label
100%
100%
GA Epic Resources section
0%
100%
Work-type suffixes in GA stories
0%
100%
- Repository
- PagerDuty/ai-forward-planning
- Commit
585e8a6
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.