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.
92
—
Does it follow best practices?
Impact
99%
3.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Jira ticket create and close workflow
Heredoc stdin pipe
0%
100%
--raw flag on create
0%
100%
--no-input on create
100%
100%
Wiki markup in description
0%
100%
Exactly one primary label
100%
100%
Edit before move
0%
100%
did-you-use-ai? slug
0%
100%
story-points slug
0%
100%
--no-input on edit
0%
100%
Transition name
0%
100%
Jira CLI workflow script with correct flag usage and In Progress transition
Tool detection check
80%
100%
No ORDER BY in JQL
0%
100%
--order-by flag used
0%
100%
--plain flag on list
0%
100%
--paginate flag used
0%
100%
Story points set before/during transition
100%
100%
Transition name not status name
0%
100%
--no-input on edit/move
0%
70%
Single tool after detection
100%
100%
Scope creep ticket creation, cross-project linking, and Internal Review transition with wiki markup
Follow-up description references parent
100%
100%
Wiki markup in description
0%
100%
Stdin heredoc for multi-line description
0%
100%
--raw flag on create
0%
100%
--no-input flag on create/edit
100%
100%
Follow-up ticket component
100%
100%
Follow-up ticket label
100%
100%
Related link type for follow-up
60%
100%
Documents link type for engineering ticket
0%
100%
PR URL in comment
100%
100%
User mention syntax
0%
100%
e765459
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.