From jira-workflows
Use when user asks to create a Jira issue, says "create task", or needs a well-structured issue with clinical context and PubMed references
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira-workflows:issue-createThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create well-researched Jira issues with proper structure, team assignments, and clinical references.
Create well-researched Jira issues with proper structure, team assignments, and clinical references.
pubmed_search_articles to find paperspubmed_fetch_contents for detailsAsk the user if anything is unclear:
| Teams Involved | Structure |
|---|---|
| 1 team | Single issue |
| 2+ teams | Epic + linked issues per team |
Assign based on domain:
| Team | Scope |
|---|---|
| Backend/Algorithms | Measurements, algorithms, workspaces, data pipelines |
| Frontend/UI | Visualization, 3D rendering, user interface |
| Design | UX, mockups, user flows |
| Clinical | Validation, radiology review |
Ask the user for specific assignees if not obvious from project context.
Required sections:
Optional sections (add when relevant):
## Overview
[Brief description of what needs to be done and why]
## Clinical Context
[Medical background, relevant thresholds, guideline references]
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Add tests with edge cases
- [ ] Google-style docstrings with references
## Acceptance Criteria
- [ ] Tests pass
- [ ] Pre-commit clean
- [ ] Measurements match published values (if clinical)
## References
- Author et al. Title. Journal. Year.
https://doi.org/10.xxxx/xxxxx
jira_create_issue — create issuesjira_create_issue_link — link related issuespubmed_search_articles — find literaturepubmed_fetch_contents — get article detailsnpx claudepluginhub amplifier-ai/amplifier-skills --plugin jira-workflowsCreates Jira issues via CLI flags or work-item files. Converts Markdown body to ADF, previews payload, requires confirmation, then POSTs to Jira.
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.
Task creation for issue trackers — structured descriptions, acceptance criteria, field categorization, and tracker linking. Invoke whenever task involves creating work items in any issue tracker — bugs, features, stories, tasks, or any tracked work from standalone requests or decomposition documents.