next-selection

Selects and groups prioritized backlog issues into a balanced Next column round.

1|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/jpalczewski/kajet-turbo --skill next-selection-jpalczewski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: next-selection
Source: https://github.com/jpalczewski/kajet-turbo/tree/main/.claude/skills/next-selection
Command: npx skills add https://github.com/jpalczewski/kajet-turbo --skill next-selection-jpalczewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding what to work on next from a large, prioritized backlog is slow and error-prone: issues may be obsolete, blocked by unfinished dependencies, or unbalanced across fixes, refactors, and features. This Skill turns a triaged Backlog into a concrete, dependency-safe Next column proposal for the kajet-turbo project board. ## Core Features & Use Cases - Balanced round building: Selects roughly 15 issues (counting In Progress) with a deliberate mix of fixes, refactors, and features, defaulting to P0/P1 items and filling from P2. - Staleness and dependency checks: Verifies every candidate against origin/main, flags obsolete issues as clean-ups, and enforces blocked-by chains so no issue enters Next without its blocker. - PR grouping and approval flow: Groups issues touching the same files into PRs, proposes the round in a table with near-misses and clean-ups, and applies changes to the board only after user approval. - Use Case: Your Next column has run dry after a sprint. Run this Skill to collect the board state, propose a balanced round of 15 issues grouped into 4 PRs, swap in alternatives, and apply the approved selection. ## Quick Start Ask the assistant to plan what goes into the Next column from the prioritized Backlog and propose the round for approval.

Frequently Asked Questions about next-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which backlog issues to work on next?▼

Triage the backlog with priorities first, then select a balanced round: include P0 and P1 items by default, fill the mix from P2 across fixes, refactors, and features, and group issues touching the same files into PRs. Verify each candidate is not obsolete before selecting it.

How do I handle blocked-by dependencies when planning a sprint?▼

Treat a blocked-by chain as an ordered unit: include the head of the chain and only as many later links as the round can reach. Never select an issue whose blocker is neither in the round nor already In Progress.

How many issues should go into a Next column?▼

This workflow targets about 15 issues, counting items already In Progress, since other sessions move work concurrently. The PR count is reported alongside because it is a truer measure of the round's size than the raw issue count.

What happens if a backlog issue is already obsolete?▼

Each candidate is verified against origin/main before selection. Issues that are obsolete, already fixed, or absorbed by another PR are excluded from the round and reported as clean-ups to close, rather than being scheduled.

Does the skill change the project board automatically?▼

No. It proposes the round as a table with proportions, PR count, near-misses, and clean-ups, then asks for approval. Only after approval does it re-check the board state and apply the status changes with board.py.