Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add juanmhidalgo/claude-plugins --skill prd-best-practicesgit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/prd-best-practices)<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/prd-best-practices"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/prd-best-practices/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/juanmhidalgo/claude-plugins/prd-best-practices"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/prd-best-practices.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.00042 | $0.00856 |
| Opus 5 | $0.00021 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
prd-best-practices 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Best Practices
Core Principles
Focus on Observable Behavior
- Describe what users see and experience
- Let developers investigate implementation details
- Avoid specifying classes, APIs, or technical architecture
Keep it concise
- PRDs are for scoping, not full specs
- 1-2 pages max for most features
- If it's longer, break into smaller features
Make it testable
- Every criterion should be verifiable by observing the product
- Use concrete, measurable outcomes
- Avoid vague terms like "fast", "easy", "better"
Writing Good Acceptance Criteria
Focus on what the user experiences, not how it's built.
Good (observable behavior):
- User can sign in with their Google account
- Session stays active for 24 hours
- If login fails, error message shows with retry option
- Admin can connect multiple workspaces simultaneously
Bad (implementation details):
- Implement OAuth 2.0 with PKCE flow
- Store JWT tokens in Redis with 24h TTL
- Use retry logic with exponential backoff
- Create WorkspaceConnection model with foreign key to User
Writing User Stories
Use the format: As a [role], I want [action] so that [benefit]
Good:
- As an admin, I want to connect my Teams workspace so that my team receives notifications
- As a user, I want to reply from Teams so that I can take action without opening another app
Bad:
- As a developer, I want to use the Teams API to implement webhooks
- As a system, I want to validate OAuth tokens to authenticate users
Section Guidelines
Overview
- 2-3 sentences max
- Answer: What problem? What solution?
- Include the user/business benefit
Goals
- 2-4 business or user objectives
- Start with action verbs (Enable, Reduce, Improve, Expand)
- Tie to measurable outcomes when possible
User Stories
- Cover main user roles affected
- Focus on user value, not system behavior
- 2-5 stories typically enough
Acceptance Criteria
- Observable from user perspective
- Include happy path + key error cases
- Checkboxes for tracking
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.
- 5d ago First seen · 126 lines · 42 tokens per session scan A aaed076163f2
prd-best-practices is a skill published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 856 once invoked, about $0.0002 per session on Opus 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
requirements-elicitation
Turns vague intent into testable requirements.
software-design-creation
Create software design specifications for new features or standalone software. Use when the user needs help turning a brief idea into a concrete design spec by eliciting missing requirements, clarifying scope, defining users and constraints, outlining architecture and interfaces, identifying risks and assumptions, and…
acceptance-criteria-given-when-then
Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords…
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
project-specification
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
handoff
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…