suggesting-next-steps

Prioritize your project backlog by gathering signals from local git state, open GitHub issues, and PRs to produce a prioritized next-steps plan. The skill analyzes git status, branch logs, and open tickets to recommend what to work on next.

To figure out what to work on next after a break, analyze your repository's current state. This skill reviews git history, stashes, and open GitHub issues to generate a prioritized action plan for resuming development.

Yes, you need the gh CLI installed to query open GitHub PRs and issues for sprint planning. The skill requires file read access and gh CLI to gather the GitHub signals needed for backlog prioritization.

No, you cannot use this approach to automatically update milestones because it is a read-only skill. It gathers and organizes information from git and GitHub to suggest prioritized next steps, but does not make any changes to your project.

Local git state contributes to backlog prioritization by providing current context. The skill checks git status, active branches, recent commit logs, and stashed changes to understand what work is in progress and suggest the next logical steps.

The main limitation is that this project planning approach is strictly read-only and relies entirely on local git state and GitHub data. It cannot make changes to your repository and only suggests priorities based on existing issues, PRs, and commit history.