next-issue

Rank open GitHub issues by priority and staleness for backlog triage.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill next-issue-mujtaba3b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-issue
Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/pm/skills/next-issue
Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill next-issue-mujtaba3b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide which existing GitHub issue to tackle next when the backlog is full and you need a clear, priority-aware recommendation.

Core Features & Use Cases

  • Backlog Triage: Pulls open issues from the configured source or current repo and filters out anything that is not pickable.
  • Priority Ranking: Sorts issues by priority and age so the most urgent, least stale work rises to the top.
  • Selection Handoff: Shows the top options, explains the recommendation, and prepares a clean handoff for planning the chosen issue.

Quick Start

Ask the assistant which GitHub issue you should work on next from the current backlog.

Frequently Asked Questions about next-issue

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

FAQPage Schema
How do I prioritize my GitHub backlog to find the best issue to work on next?

To prioritize your GitHub backlog, this Skill ranks open issues by filtering out unpickable tasks, applying priority bucketing, and adding staleness penalties so the most urgent issues surface to the top.

What is backlog triage and how does issue ranking work for GitHub projects?

Backlog triage evaluates open GitHub issues to determine their priority. Issue ranking works by hydrating issue data, excluding linked pull requests, and sorting remaining pickable issues by priority and age.

How do I automatically filter out linked pull requests when triaging GitHub issues?

When triaging GitHub issues, the ranking process automatically applies linked-PR exclusion to filter out active pull requests, ensuring only pickable unresolved issues are considered for your next task.

Does this backlog triage tool work with configured GitHub Projects or only single repositories?

This backlog triage tool applies to both individual repositories and configured GitHub Projects, pulling open issues from the designated source to identify the most urgent next task.

What happens after I pick the highest priority GitHub issue from the ranked list?

After picking the highest priority GitHub issue, the tool prepares a prompted handoff to plan-eng-review, showing the top options and explaining the recommendation so you can plan the chosen issue.