PRP is a collection of prompts and workflows for AI-assisted software development with Claude Code. Its Product Requirement Prompts combine product requirements, selected codebase context, and an execution runbook so a coding agent can implement a vertical slice of software. The catalogue entries are the project’s own skills, agents, instructions, hook, and plugin workflows.
Borrowing it
Nothing to install: this file belongs to Wirasm/prp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Wirasm/prp/development/.agents/skills/prp-prd-update/SKILL.mdgit clone --depth 1 https://github.com/Wirasm/prpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wirasm/prp/prp-prd-update)<a href="https://agentmods.dev/skills/wirasm/prp/prp-prd-update"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-prd-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wirasm/prp/prp-prd-update"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-prd-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.00470 |
| Opus 5.5 | $0.00024 | $0.00188 |
| Sonnet 5.5 | $0.00012 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
prp-prd-update scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Arguments:
$ARGUMENTS(and$1,$2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.
Update PRD Phase
Maintain one source PRD's implementation lifecycle without changing its requirements or product decisions.
Arguments: $ARGUMENTS
Resolve and verify
Require an explicit stage, PRD path, and phase number. Read the entire PRD and select the phase by its exact number, never by a fuzzy title match. Stop if the phase is missing, duplicated, or the requested transition conflicts with recorded state.
The Implementation Phases table must have Plan, Report, and PR columns. When reading an older PRD, rename PRP Plan to Plan and add missing columns without losing any row data or changing unrelated content.
Apply the stage
planned— require the plan file to exist. SetStatustoin-progressand record its absolute path inPlan.implemented— require the plan and report files to exist and verify that the PR URL identifies an open or merged PR for the current repository. KeepStatusasin-progressand record the absolute plan path, absolute report path, and PR URL.merged— verify through GitHub that the recorded or supplied PR is merged. SetStatustocompleteand preserve all artifact links.
Never mark a phase complete merely because implementation passed or a PR exists. Never move status backward, replace a conflicting artifact silently, infer a phase number, or modify another phase. Repeating the same valid update must be harmless.
Verify and report
Re-read the exact phase row after editing. Confirm its status and links match the requested stage and that the Markdown table remains valid. Return the PRD path, phase number, resulting status, and recorded links. Do not create a separate report artifact.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 31 lines · 61 tokens per session scan A e661eb3d745a
prp-prd-update is a skill published in the GitHub repository Wirasm/prp (2,264 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 470 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…