Provides guidance on issue/ticket workflow management during development sessions. Supports multiple project management providers (Linear, JIRA, etc.). Use when working on issues, updating tickets, or managing state transitions.
This skill guides you through managing issue/ticket states during development work across multiple project management providers.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.
| Provider | URL Pattern | MCP Required |
|---|---|---|
| Linear | https://linear.app/*/issue/* | linear@claude-plugins-official |
| JIRA | https://*.atlassian.net/browse/* | JIRA MCP (Atlassian) |
You MUST update issues:
You SHOULD update issues:
You MUST automatically detect providers from these formats:
https://linear.app/*/issue/*https://*.atlassian.net/browse/* or https://*.jira.com/browse/*[A-Z]{2,10}-\d+ (e.g., CIR-123, PROJ-456)Before performing any operation, you MUST verify the required MCP is available.
If MCP is NOT available:
The [Provider] MCP is not configured. To enable issue tracking:
1. Install the plugin: `claude plugin install [provider]@claude-plugins-official`
2. Authenticate when prompted
Would you like to continue without issue tracking?
You MUST NOT attempt to call unavailable MCP tools.
// Get issue
mcp__plugin_linear_linear__get_issue({ "id": "CIR-123" })
// List team statuses
mcp__plugin_linear_linear__list_issue_statuses({ "team": "team-id" })
// Update issue
mcp__plugin_linear_linear__update_issue({ "id": "uuid", "state": "In Progress" })
// Add comment
mcp__plugin_linear_linear__create_comment({ "issueId": "uuid", "body": "Comment" })
// Get issue
mcp__atlassian_jira__get_issue({ "issueKey": "PROJ-456" })
// Get transitions
mcp__atlassian_jira__get_transitions({ "issueKey": "PROJ-456" })
// Transition issue
mcp__atlassian_jira__transition_issue({ "issueKey": "PROJ-456", "transitionId": "21" })
// Add comment
mcp__atlassian_jira__add_comment({ "issueKey": "PROJ-456", "body": "Comment" })
/issue-work [issue-id-or-url] - Start working on an issue (moves to In Progress)/issue-update [comment] - Add progress update or modify issue/issue-done [comment] - Complete work (moves to Done)You MUST track within the conversation:
Output format: Active issue: [ID] ([Provider])
This enables subsequent commands without re-specifying the issue or provider.