Use this skill for any Jira operation in the DOCSP project — creating, viewing, searching, updating, transitioning, commenting on, or linking tickets. Also handles follow-up ticket creation to manage scope creep. TRIGGER when: user mentions a DOCSP-XXXXX ticket number or any Jira ticket URL; user asks to view, open, check, update, transition, close, comment on, link, or search tickets; user references "the ticket", "the Jira", or "open a ticket". SKIP: GitHub issues; non-Jira platforms; questions unrelated to ticket operations.
89
88%
Does it follow best practices?
Impact
88%
2.25xAverage score across 3 eval scenarios
Passed
No known issues
Ticket creation with correct CLI flags and markup
Stdin piping for description
0%
100%
No -b heredoc substitution
100%
100%
Wiki markup headers
100%
100%
No Markdown in description
100%
100%
--no-input flag
0%
100%
--raw flag with stdin
0%
100%
Exactly one primary label
0%
100%
Correct priority format
0%
100%
Project DOCSP
0%
100%
Valid issue type
100%
100%
Search, transition, and PR link comment workflow
ORDER BY as CLI flag
0%
100%
No ORDER BY in JQL
0%
100%
--plain for list output
0%
100%
Transition name not status name
33%
50%
Story Points Estimate on In Progress
0%
100%
PR link comment posted
100%
100%
PR comment on Internal Review
0%
0%
--no-input on edit commands
0%
100%
JQL filters current user
100%
100%
Correct ticket key used
100%
100%
Ticket closure with required fields and scope-creep follow-up
Story Points set before close
0%
100%
Did you use AI field set
50%
100%
Resolution set during Close transition
100%
0%
CLI: fields before move
0%
100%
Valid resolution value
100%
0%
Follow-up ticket created
100%
100%
Follow-up references originating ticket
100%
100%
Follow-up uses wiki markup
62%
100%
Tickets linked as Related
30%
100%
Story points moderate scale
0%
100%
--no-input on edit/create
0%
100%
5985af5
Table of Contents
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.