shreypurohit/jira-dev-workflow-plugin
Task-oriented Jira development workflow plugin using official Atlassian Rovo MCP v2. Skills cover reading tickets, planning (including attached mockups/specs), status transitions, worklog/time-tracking, review prep, attachment downloads, Jira-aware Git branches, sprints, and linking development work through natural-language prompts.
Download files attached to a Jira issue or comment via the authenticated MCP server (screenshots, mockups, spec docs), instead of an unauthenticated web fetch. Use when the intent is "get/show me the files"; for planning that needs the attachments use jira-plan.
Create a Git branch from a Jira issue key with smart naming and repository safety checks. Use when the user asks to create or set up a branch for a ticket.
Post a free-text progress, note, or completion comment on a Jira issue. Use for prose updates the user dictates or asks you to compose — NOT for linking git branches/commits/PRs (use jira-link-work) and NOT for status changes (use jira-update-status).
Wrap up a finished Jira issue — post a confirmed completion comment AND transition it to the final Done status in one flow. Use only for final completion; for a bare status change use jira-update-status.
Link git branches, commits, or pull requests to a Jira issue by posting a comment built FROM git data (traceability between code and ticket). Use only when the content comes from git — for free-text prose comments use jira-comment.
Analyze Jira issue requirements and create structured implementation plans, reading any attached mockups/screenshots/spec docs first. Use when the user asks to plan, break down, or analyze what to build for a ticket.
Read, summarize, and search Jira issues through natural language. Use when looking up a ticket, extracting acceptance criteria, or listing issues with JQL.
Prepare a Jira issue for review — generate a PR/MR description from acceptance criteria and the local git diff, then optionally transition to the review status. Use to get a ticket review-ready; for a bare status change use jira-update-status.
Show current sprint status, your assigned tickets, and blockers at a glance. Use for sprint workload, board status, blockers, or standup prep — not for generic issue search.
Begin work on a Jira issue by transitioning it to In Progress. Use only for starting work; for any other status change use jira-update-status, and use jira-branch separately to create a Git branch.
Transition a Jira issue to an arbitrary status via dynamic discovery. Use for general status changes EXCEPT specialized flows — starting work (jira-start-work), final completion (jira-complete), and review prep with a PR description (jira-review-prep).
Log time spent on a Jira issue via natural language (worklog entries). Use for tracking/recording time against a ticket — NOT for status changes (use jira-update-status) or comments (use jira-comment).