菜单
Render the open work of a repository as something worth looking at, so the maintainer can see what to take next. Deliberate invocation only — /prp-worklist.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Wirasm/prp --skill prp-worklist命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Autonomously owns one workstream from an issue, PRD, document, existing plan, or free-form request through planning, implementation, pull request, independent review, corrections, and green CI. Always use when the user asks to implement or ship work end to end, take an issue or idea to a reviewed PR, run plan to PR, invokes $prp-issue, or when prp-orchestrate needs an end-to-end delivery engine.
Autonomously owns one workstream from an issue, PRD, document, existing plan, or free-form request through planning, implementation, pull request, independent review, corrections, and green CI. Always use when the user asks to implement or ship work end to end, take an issue or idea to a reviewed PR, run plan to PR, invokes /prp-issue, or when prp-orchestrate needs an end-to-end delivery engine.
Implements and validates existing PRP plans and corrects reviewed or failing-CI pull requests. Always use when executing an implementation plan, implementing an issue that already has a local or published plan, correcting a PR from a PRP review report or CI failure, when another PRP workflow reaches its implementation or correction step, or when the user invokes $prp-implement.
基于 SOC 职业分类
正在显示 SKILL.md
| name | prp-worklist |
| description | Render the open work of a repository as something worth looking at, so the maintainer can see what to take next. Deliberate invocation only — /prp-worklist. |
| argument-hint | [repo] — defaults to the current repository |
| disable-model-invocation | true |
| context | fork |
Incubating. Deliberately underspecified. Make your own judgements, then say what you chose and why — the good choices get recorded and prescribed later. Do not wait for a spec that does not exist yet.
Render the open issues and PRs of a repository as an artifact the maintainer can look at, and offer it. Not a list of everything — a view of what to take next.
A tracker sorts by number and shouts every label equally loudly. That is the tool's view, not the maintainer's. Produce the maintainer's view.
Read the tracker with gh. Then decide what is worth showing and how to show it.
Considerations, not fields to emit. Weigh them, drop the ones that do not apply, add what the repository makes obvious:
Yours to decide. Markdown or HTML, grouped or ranked, dense or spacious — whatever makes the answer to "what do I take next" obvious in a glance.
Then offer it rather than pasting it: write the file to this project's ~/.prp/<key>/ store
and print a link the operator can open. If a helm-canvas skill is available, follow it.
End with a short note: what you grouped by, what you left out, what you could not tell from the tracker alone. That note is the point of this skill being loose — it is how the shape gets decided by evidence rather than up front.
If something here got in your way, say that too.
