What problem does it solve?
Issue trackers sort by number and treat every label equally, making it hard for a maintainer to see what to work on next. This Skill reads a repository's open issues and PRs and produces a curated view of what is actually worth taking next.
Core Features & Use Cases
- Maintainer-focused triage: Reads the tracker with the GitHub CLI (
gh) and weighs considerations like blocked-vs-takeable, staleness, near-duplicates, ownership, and blast radius.
- Artifact output: Writes the rendered view (Markdown or HTML, shape decided by the agent) to the project's
~/.prp/<key>/ store and prints a link instead of pasting content.
- Transparent reasoning: Ends with a short report of what was grouped, what was left out, and what could not be determined from the tracker alone.
- Use Case: A maintainer returning to a repository after two weeks runs the skill to get a single glanceable page showing which issues are stale, which are blocked on decisions, and which are ready to pick up now.
Quick Start
Run /prp-worklist against the current repository to generate a prioritized view of open issues and PRs.