Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install planningWrote 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/melodic-software/claude-code-plugins/prd)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/prd"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/prd/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/melodic-software/claude-code-plugins/prd"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00137 | $0.06435 |
| Opus 5.5 | $0.00055 | $0.02574 |
| Sonnet 5.5 | $0.00027 | $0.01287 |
| Haiku 4.5 | $0.00014 | $0.00643 |
Grade A, and why
prd 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 27d 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.
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository context. Gather first
Collect these with individual Bash calls, one command per call, never combined into a single invocation:
- Current branch,
git branch --show-current - Recent commits,
git log --oneline -5 - Working tree status (empty = clean),
git status --porcelain | head -10
The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.
Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git. The dated record for that composition claim is the worktree skill's reference/gather-block.md, "The pre-compute block runs as one shell invocation".
Variables
Arguments: $ARGUMENTS
Purpose
Most product-feature rework comes from skipping the what for whom and why layer and jumping straight to how. /planning:prd produces the lockable product intent contract: what we are building, for which users, against what measurable success, before any engineering plan, exploration, or research begins.
This is the product-intent stage. Upstream of exploration, upstream of /planning:plan, and may run before or alongside /planning:interview depending on task shape:
/planning:prd. Answers what should we build, for whom, and why. Outcome-focused. Required for new user-facing features, business-driven changes, cross-team initiatives/planning:interview. Answers what is the engineering contract for this task. Constraint and acceptance-criteria focused. Required whenever intent is fuzzy or underspecified, regardless of source- Complementary, not redundant. A product feature usually wants both:
/planning:prd(product intent) →/planning:interview(engineering contract) → exploration → research →/planning:design→/planning:plan. Engineering-internal work skips/planning:prdentirely
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago Changed f254a0b7d03a
- 1mo ago Changed b862063d5fd0
- 1mo ago Changed · +3 lines c62049be20f6
- 1mo ago Changed · +100 lines · +13 tokens per session 5c23860677ec
- 1mo ago Changed · +2 lines c45de00a1aac
- 1mo ago Changed · +12 lines · +2 tokens per session 7432f203ac6b
- 1mo ago First seen · 234 lines · 122 tokens per session scan A 97259911e310
prd is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 6,435 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.
hiring-craft
Use when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should we hire X", "I need…