From jira-workflows
Use when user asks to improve, refine, or enhance an existing Jira issue with better structure, clinical context, or PubMed references
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira-workflows:issue-refineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Enhance existing Jira issues with research, proper structure, and clinical context.
Enhance existing Jira issues with research, proper structure, and clinical context.
Fetch the issue — read current content via jira_get_issue
Identify gaps:
| Gap | Enhancement |
|---|---|
| No clinical context | PubMed research + thresholds |
| Vague requirements | Structured bullet list |
| No acceptance criteria | Testable conditions |
| No references | Citations with DOI/PMID |
| Poor formatting | Markdown structure |
Research — PubMed search and/or codebase analysis as needed
Show before/after — present proposed changes to the user
Wait for approval — apply only after explicit confirmation
Update the issue — apply changes via jira_update_issue
jira_get_issue — fetch current issuejira_update_issue — apply changespubmed_search_articles — find literaturepubmed_fetch_contents — get article detailsnpx claudepluginhub amplifier-ai/amplifier-skills --plugin jira-workflowsRefines brief bug, feature, or refactor descriptions into structured issues with technical context, code links, and details for developers and AI agents.
Fetches a JIRA issue and distills it into a structured task with acceptance criteria, sprint context, and codebase analysis. Surfaces missing criteria, scope, and risks, and can enrich the JIRA issue with analysis or spawn sub-tickets.
Updates GitHub issue descriptions with structured analysis (summary, requirements, references, implementation plan, impact scope) based on issue number, request, code, docs, and designs.