Menu
Pull a Jira ticket with linked docs, tickets, comments, and PRs. Produces an actionable summary with assessment and open questions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Config-driven visible plan-to-PR workflow for Workbench engineering work. Use for agent-flow, full lifecycle, visible agents, Helix-style implementation, cross-repo context, HTML plans, PR breakdowns, small or stacked PRs, reviewer packets, review from packet, Claude/Codex pairing, worktrees, Jira/PR handoffs, continuation handoffs, or approved bypass of detailed PR slicing.
Freeform ideation and structured shortlisting. Generates 8-10 approaches including wild cards, then converges on 2-4 viable options with tradeoffs. Use before /forge or standalone for any creative exploration.
Read Outlook Web calendar via Chrome and extract meeting data for capacity planning. Writes to context/active/calendar.md so other skills use real numbers.
Show remaining capacity today and this week by reading daily and weekly plans. Flags overcommitment. Use when checking if there's room for more work.
Read and critically summarize a Confluence document. Surfaces key decisions, gaps, open questions, and suggests review questions.
Create a release branch and managed _release worktree in a Workbench repo using canonical Python worktree tooling. Use when the user wants to cut a release, create a release branch, start a release process, preview the next release branch name, or keep release work out of main/develop.
| name | jira-review |
| description | Pull a Jira ticket with linked docs, tickets, comments, and PRs. Produces an actionable summary with assessment and open questions. |
| metadata | {"workbench.argument-hint":"<ticket-id>"} |
Pull a ticket and give a comprehensive, actionable summary.
Jira project keys and ticket patterns are defined in config.yaml under jira.projects.
The user will provide a Jira ticket ID (e.g., matching one of the patterns defined in config.yaml: jira.projects[].ticket_pattern).
Use mcp__claude_ai_Atlassian__getJiraIssue to get the full ticket details.
From the ticket data:
mcp__claude_ai_Atlassian__getConfluencePage.mcp__claude_ai_Atlassian__getJiraIssueRemoteIssueLinks.Summarize the comment thread, highlighting:
## [TICKET-ID] Title
**Status**: X | **Assignee**: Y | **Priority**: Z
### What This Is About
(1-3 sentences)
### Key Decisions (from comments)
- Decision 1
- Decision 2
### Open Questions
- Question with no answer yet
- Ambiguity in requirements
### Linked Context
- [TICKET-ID] Related ticket (status: X)
- Confluence: "Doc Title" โ (1-line summary)
- PR #NNN โ (status: open/merged)
### Acceptance Criteria
(From the ticket, or flag if missing)
### Assessment
(Is it well-defined? Missing info? Ready to work on? Blocked?)