Scrum next-work triage
Recommend work the user can start now. Treat the board as a queue, not as proof that an item is actionable.
Triage
- Identify the current user and active sprint.
- Record any work the user says is already running elsewhere as occupied. Keep it out of recommendations until the user says it is free.
- Build candidates in this order:
- assigned implementation or refinement work that is ready to start;
- the user's own open PRs that need a response (new review feedback, requested changes, failing checks, merge conflicts, or unresolved review threads awaiting the author);
- unassigned, ready implementation or refinement work in the active sprint;
- open PRs authored by someone else that still need the user's review.
- Exclude QA work, tickets in QA review, tickets the user implemented, reviews the user has already approved on the current head, and work already in progress elsewhere. Do not exclude the user's own PRs when they need author action.
Evidence
For every candidate, verify the evidence before recommending it:
- Jira: active-sprint membership, status, assignee, rank, dependencies, and ticket readiness.
- GitHub (review): PR exists and is open; author is not the user; user has not approved the current head; checks, mergeability, and unresolved review threads are known.
- GitHub (own PR): PR is open and authored by the user; there is new activity since the user's last response (review comments, review decisions, check runs, or mergeability) that requires author action.
- Scope: the work is implementation, refinement, or code review—not QA.
Use narrow queries first. Fetch full ticket or PR details only for the leading candidates.
Choice
Recommend one item, with its link and the immediate first action. State why it is actionable using the evidence above.
If no active-sprint item qualifies, say so plainly. Offer the highest-ranked unassigned backlog candidate only after marking it as outside the active sprint, or ask whether the user wants to pull backlog work.
Completion
Finish only when the recommendation is actionable for this user now, or when the absence of such work is explicit.
1---2name: scrum-next3description: Scrum board next-work triage. Use when asked what to work on next, what is next on the board, or to choose an actionable Jira task, updates on the user's open PRs, or a PR review.4metadata:5 source: https://skillmd.com/skills/lucavb/scrum-next6---78# Scrum next-work triage910Recommend work the user can start now. Treat the board as a queue, not as proof that an item is actionable.1112## Triage13141. Identify the current user and active sprint.152. Record any work the user says is already running elsewhere as **occupied**. Keep it out of recommendations until the user says it is free.163. Build candidates in this order:17 1. assigned implementation or refinement work that is ready to start;18 2. the user's own open PRs that need a response (new review feedback, requested changes, failing checks, merge conflicts, or unresolved review threads awaiting the author);19 3. unassigned, ready implementation or refinement work in the active sprint;20 4. open PRs authored by someone else that still need the user's review.214. Exclude QA work, tickets in QA review, tickets the user implemented, reviews the user has already approved on the current head, and work already in progress elsewhere. Do not exclude the user's own PRs when they need author action.2223## Evidence2425For every candidate, verify the evidence before recommending it:2627- **Jira:** active-sprint membership, status, assignee, rank, dependencies, and ticket readiness.28- **GitHub (review):** PR exists and is open; author is not the user; user has not approved the current head; checks, mergeability, and unresolved review threads are known.29- **GitHub (own PR):** PR is open and authored by the user; there is new activity since the user's last response (review comments, review decisions, check runs, or mergeability) that requires author action.30- **Scope:** the work is implementation, refinement, or code review—not QA.3132Use narrow queries first. Fetch full ticket or PR details only for the leading candidates.3334## Choice3536Recommend one item, with its link and the immediate first action. State why it is actionable using the evidence above.3738If no active-sprint item qualifies, say so plainly. Offer the highest-ranked unassigned backlog candidate only after marking it as outside the active sprint, or ask whether the user wants to pull backlog work.3940## Completion4142Finish only when the recommendation is actionable for this user now, or when the absence of such work is explicit.