Stats
Actions
Tags
From cowork-with
Use when the user works with or mentions Jira issues, tickets, stories, bugs, tasks, sprints, epics, or any agile workflow
How this skill is triggered — by the user, by Claude, or both
Slash command
/cowork-with:cowork-with-jiraThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Agile Jira workflow for Claude Code via the Atlassian Rovo MCP server.
Agile Jira workflow for Claude Code via the Atlassian Rovo MCP server.
Requires globally installed Atlassian MCP server (named atlassian). If not set up, run /cowork-with:cowork-with-onboarding.
No type prefix. Jira tracks issue types natively — never prefix with [Feature], Bug:, etc.
Plain text only. Jira does NOT render Markdown — no ##, **, - [ ], or backtick fences. Use Jira wiki markup or plain text with simple line breaks.
Every issue description MUST include these sections:
Background
Why this issue exists. What problem it solves. Any relevant context.
Acceptance Criteria
- Specific, testable criterion
- Another criterion
Do not skip Acceptance Criteria. Even for small tasks, at least one criterion is required.
Issue type names are localized — a project may use "Bug", "缺陷 Bug", "バグ", etc. Always use the explorer agent to call getJiraProjectIssueTypesMetadata first and use the exact type name returned.
| Intent | Jira Type | Label | When to use |
|---|---|---|---|
| New functionality | Story | story | User-facing feature or capability |
| Bug fix | Bug | bug | Something is broken |
| Technical work | Task | task | Maintenance, config, dependencies, refactoring |
| Research | Task | spike | Investigation or spike |
| Documentation | Task | documentation | Docs changes |
| Large initiative | Epic | epic | Groups 3+ related stories |
| Subtask | Sub-task | subtask | Discrete piece of a parent story |
Additional labels for special categories: tech-debt. If the project has existing label conventions (check recent issues), follow those instead.
Always assign to @me unless the user specifies a different assignee.
When assigning to someone other than @me, use the explorer agent to call lookupJiraAccountId to resolve their name or email to an account ID before creating or editing the issue.
Always set Medium unless specified.
| Priority | When to use |
|---|---|
| Highest | Production down, data loss, security vulnerability |
| High | Blocks other work, major user-facing issue |
| Medium | Default — standard work |
| Low | Nice-to-have, minor polish |
| Lowest | Cosmetic, trivial |
To Do → In Progress → In Review → Done
| Status | When to transition |
|---|---|
| To Do | Issue created, ready to work on |
| In Progress | User starts working on it |
| In Review | Code submitted for review (if status exists) |
| Done | Work finished and verified |
Proactive transitions: When context makes it obvious (e.g., user says "I'm working on PROJ-42"), transition to In Progress without asking.
Custom workflow handling: If a transition fails, use the explorer agent to call getTransitionsForJiraIssue to inspect available transitions and pick the closest match. Report the actual status name to the user.
Spawn via: Agent tool → name: "explorer" (the plugin ships agents/explorer.md — haiku model, read-only: MCP reads + codebase + git).
| Task | Who |
|---|---|
| Read from Jira (search, view, metadata) | explorer agent |
| Read git/gh context, explore codebase | explorer agent |
| Draft issue content (title, description, criteria) | Main model |
| Preview to user and get confirmation | Main model |
| Write to Jira (create, edit, transition, comment) | Main model |
Read (explorer agent):
getJiraIssue — read a single issue (param: issueIdOrKey)searchJiraIssuesUsingJql — search issues with JQL (param: maxResults must be number, not string)getVisibleJiraProjects — list projectsgetJiraProjectIssueTypesMetadata — issue types for a project (param: projectIdOrKey)getJiraIssueTypeMetaWithFields — field metadata for an issue type (param: projectIdOrKey, issueTypeId)getTransitionsForJiraIssue — available status transitionsgetJiraIssueRemoteIssueLinks — remote links on an issuelookupJiraAccountId — resolve user name/email to account IDatlassianUserInfo — current authenticated user infojiraRead — generic Jira REST API read (fallback for endpoints not covered above)search — cross-service Atlassian search (searches Jira + Confluence together)Write (main model, after user confirmation):
createJiraIssue — create a new issue (param: issueTypeName — NOT issueType; labels is array of strings)editJiraIssue — update an existing issue (param: issueIdOrKey; fields must be object, not JSON string)transitionJiraIssue — change issue statusaddCommentToJiraIssue — add a commentaddWorklogToJiraIssue — log work time1. `explorer` agent → Fetch project context (ALL in one batch, parallel where possible):
a. getJiraProjectIssueTypesMetadata (exact localized type names)
b. getJiraIssueTypeMetaWithFields (ALL required fields incl. custom)
c. searchJiraIssuesUsingJql "sprint in openSprints()" (active sprint name + goal)
2. Main model → Compare required fields vs. known values
If ANY required field is missing → ask user via AskUserQuestion BEFORE drafting
3. Main model → Present active sprint to user:
Show sprint name, goal, and date range
Ask: assign to this sprint, or leave unassigned?
4. `explorer` agent → Read git context + search codebase if needed for context
5. Main model → Draft title, description (plain text!), acceptance criteria
6. Main model → Preview FULL draft to user via AskUserQuestion (HARD-GATE below)
Include sprint assignment in preview if selected
7. Main model → Create issue after user approves (createJiraIssue)
8. Main model → Offer to create a feature branch (git checkout -b feat/PROJ-123-slug)
Step 1c is critical — sprint context must ALWAYS be fetched before drafting. If the JQL returns no active sprint, inform the user that no sprint is active and proceed without sprint assignment.
Step 1b reads ALL required fields for the chosen issue type. Before drafting:
customfield_10079), use AskUserQuestion to ask the user for the missing values. Do NOT attempt to create the issue with missing required fields.Fallback when creation still fails: If createJiraIssue rejects due to a required field despite passing it via additionalFields, create as Task first (fewer required fields), then use editJiraIssue with fields (object, not string) to change issue type and set the custom field. Report the workaround to the user.
For epics, sprints, sub-tasks, post-commit hook, and commit message format, see reference.md in this skill directory.
Key rules (always apply):
feat/PROJ-123-slug or fix/PROJ-123-slug. Jira auto-tracks branches containing the issue key.[PROJ-123] commit message when related to a taskexplorer agent to find related in-progress tasks/superpowers:brainstorming to explore implementation approaches./cowork-with:cowork-with-wiki to create or update documentation./cowork-with:cowork-with-figma to read design context before implementing.See reference.md for full list. Key: no sprint management, no issue links, no attachments via MCP.
npx claudepluginhub labrinyang/cowork-with-marketplace --plugin cowork-withViews Jira issues, generates branch names from tickets, creates tickets, and transitions status via Atlassian MCP. Activates on ticket key mentions or /jira command.
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.
Orchestrates 6-phase workflow (EXPLORE→PLAN→CODE→TEST→FIX→COMMIT) for Jira issues using multi-agent coordination. Manages bugs, stories, tasks, epics with progress tracking and PR linking.