From routine
Analyzes JIRA tickets to determine priority, dependency order, and layered groups. Outputs JSON plan with branch names, repo assignments, complexity, and verification hints.
npx claudepluginhub delexw/claude-code-miscThis skill is limited to using the following tools:
Analyze a set of JIRA tickets to determine optimal execution order based on dependencies, priority, and grouping. Produces grouped layers usable standalone or as a pre-step before `implement`/`forge`.
Fetches JIRA issue by key or search, distills title/description/acceptance criteria/comments into structured task, analyzes codebase for gaps/risks, optionally enriches JIRA.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Analyze a set of JIRA tickets to determine optimal execution order based on dependencies, priority, and grouping. Produces grouped layers usable standalone or as a pre-step before implement/forge.
Raw arguments: $ARGUMENTS
Infer from the arguments:
=, AND, OR)jira CLI installed and configured (https://github.com/ankitpokhrel/jira-cli)JIRA_API_TOKEN set with a valid Jira API token. Important: When checking this variable, verify at least 2 times before concluding it is not set. Never expose the value — use existence checks only.TICKET_INPUT contains =, AND, or OR (case-insensitive) to detect JQLjira issue list --jql "TICKET_INPUT" --plain --columns key,status --no-headers to resolve to ticket keys with statuses, and trim whitespace[A-Z]+-\d+mkdir -p .jira-ticket-prioritizer-tmp/ticketsjira issue view {KEY} --raw > .jira-ticket-prioritizer-tmp/tickets/{KEY}.json
node ${CLAUDE_SKILL_DIR}/../jira-ticket-viewer/scripts/parse-ticket.js < .jira-ticket-prioritizer-tmp/tickets/{KEY}.json > .jira-ticket-prioritizer-tmp/tickets/{KEY}-parsed.json
.jira-ticket-prioritizer-tmp/all-tickets.jsonpending = tickets with status "To Do" or "Backlog" — these will be scored, grouped, and placed in output layerscontext = tickets with any other status ("In Progress", "In Review", "Done", "Closed", "Resolved") — these are NOT placed in layers but are used for dependency resolution in Steps 3-5node ${CLAUDE_SKILL_DIR}/scripts/build-dependency-graph.js < .jira-ticket-prioritizer-tmp/all-tickets.json > .jira-ticket-prioritizer-tmp/graph.jsonall-tickets.json with additional softEdges and re-run build-dependency-graph.jsskipped. Write a plain-English reason that explains exactly what was found — which fields overlapped, what the textual similarity was, and why you concluded one ticket's scope is covered by the other. See references/redundancy-analysis.md for evidence string guidelinesskipped here must not appear in the scoring or grouping steps belowpending tickets — context tickets are not scored or placed in layersEXTRA_CONTEXT context as a tiebreaker or boostcontext ticket with status "Done"/"Closed"/"Resolved" → dependency is resolved, ticket proceeds normallycontext ticket with any other status (e.g. "In Progress") → mark as skipped with reason including the dependency key and its statuspending ticket in a different layer → normal layering (layer N+1 depends on layer N)excludedexcludedRead references/repo-assignment.md for the full rules. Determine repos, branch, complexity, and hasFrontend for every ticket per those rules.
.jira-ticket-prioritizer-tmp/detailed-report.json — full details including scores, justifications, dependency graph, skipped tickets, excluded tickets, and warnings.jira-ticket-prioritizer-tmp/output.json — the grouped layers object with layers, skipped, and excluded arraysoutput.json to the user. The detailed report is saved for reference but not displayed.rm -rf .jira-ticket-prioritizer-tmp| Name | When to Read |
|---|---|
| references/priority-weights.md | Step 5 — scoring rules and factor weights |
| references/output-format.md | Step 6 — report template and JSON schema |
| references/dependency-analysis.md | Steps 3-5 — dependency detection and grouping rules |
| references/redundancy-analysis.md | Step 4b — redundancy detection, weight/confidence rules, skipped entry format |
| references/repo-assignment.md | Step 5a — repo understanding, assignment rules, branch/complexity/hasFrontend |