メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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. |
| 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.
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 職業分類に基づく
