prp-worklist

Renders open GitHub issues and PRs as a prioritized maintainer worklist artifact.

2.2k|608|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-worklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-worklist
Source: https://github.com/Wirasm/PRPs-agentic-eng/tree/main/plugins/prp-core/skills/prp-worklist
Command: npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-worklist

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about prp-worklist

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

FAQPage Schema
How do I prioritize GitHub issues for what to work on next?

Run /prp-worklist against the repository. It reads open issues and PRs with the GitHub CLI and produces a curated view weighing blocked-vs-takeable status, staleness, near-duplicates, ownership, and blast radius.

How to detect stale or duplicate GitHub issues automatically?

The skill flags issues whose premise has moved, such as deleted code or closed blockers, and surfaces near-duplicates that describe the same underlying problem. These signals are weighed when building the maintainer's view.

Does prp-worklist require the GitHub CLI?

Yes, it reads the tracker using the gh command-line tool, so gh must be installed and authenticated against the target repository. It defaults to the current repository but accepts a repo argument.

Where does the generated worklist output get saved?

The rendered artifact is written to the project's ~/.prp/<key>/ store rather than pasted into the conversation. The skill prints a link the operator can open, and follows a helm-canvas skill if one is available.

Can I control the format of the worklist output?

The shape is deliberately left to the agent: Markdown or HTML, grouped or ranked, dense or spacious. The skill ends with a report explaining what was grouped, omitted, and undeterminable so conventions can be prescribed later.