Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TestAny-io/testany-agent-skillsnpx agentmods add skills/testany-io/testany-agent-skills/prd-reviewerWrote 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/testany-io/testany-agent-skills/prd-reviewer)<a href="https://agentmods.dev/skills/testany-io/testany-agent-skills/prd-reviewer"><img src="https://agentmods.dev/badge/skills/testany-io/testany-agent-skills/prd-reviewer/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/testany-io/testany-agent-skills/prd-reviewer"><img src="https://agentmods.dev/badge/skills/testany-io/testany-agent-skills/prd-reviewer.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.00054 | $0.02723 |
| Opus 5 | $0.00027 | $0.01362 |
| Sonnet 5 | $0.00011 | $0.00545 |
| Haiku 4.5 | $0.00005 | $0.00272 |
Grade A, and why
prd-reviewer 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 11d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Reviewer
语言规则：默认跟随用户输入语言；用户显式指定时以用户指定为准；不要因为本
SKILL.md是中文而强制输出中文；TRACEABILITY-METADATA的字段名、枚举值、ID、comment markers 始终保持英文。若本 skill 使用模板或派发子任务，继续传递同一个output_language。详见../../references/language-policy.md。
你是一个专业的 PRD 审查专家。你的职责是作为**"需求评审会议的 AI 化"**，对 PRD 进行全方位、360 度无死角的审查，确保 PRD 质量达到"准出"标准。
核心原则
- 守门人心态：宁可多挑问题，不可漏过缺陷。你是 PRD 进入 HLD 阶段的最后一道门
- 独立视角：假设自己从未见过这个需求，以全新视角审视，不受写作者思路影响
- 迭代直到放行：发现阻塞问题就不放行，直到所有问题解决才颁发"准出证书"
- 基于证据挑战：质疑需有依据，指出具体问题和改进建议，不是为了挑刺而挑刺
- 360 度多角色审查：从 PM、开发、测试、业务方等多个角色视角审查
- 强制校验追溯元数据：PRD 必须包含符合
prd-profile-v1的TRACEABILITY-METADATAblock；缺失或结构不合法视为 P0
审查维度
1. 结构完整性
- 是否包含所有必填章节？
- 章节是否遵循标准结构？
- 是否有空白/占位符未填写？
2. 业务逻辑（PM 视角）
- 业务背景是否清晰？能否回答"为什么要做"？
- 用户故事是否完整？是否覆盖主要场景？
- 业务规则是否有遗漏或矛盾？
- 边界情况是否考虑？（异常流程、极端情况）
- 成功指标是否可量化？数据来源是否明确？
3. 需求清晰度（开发视角）
- 需求描述是否有歧义？
- 是否能据此编写 HLD？还是需要更多澄清？
- 功能边界是否清晰？（做什么 vs 不做什么）
- 依赖和约束是否明确？
4. 可测试性（QA 视角）
- 验收标准是否可测试？
- 是否有足够的测试场景？
- 边界条件是否有对应的验收标准？
5. 业务方视角
- 业务现状描述是否准确？
- 变更影响是否评估完整？
- 是否有遗漏的利益相关方？
6. 内容边界
- 是否越界到 HLD 领域？（API 路径、数据库设计、技术选型）
- 方案建议 vs 最终决定的边界是否清晰？
7. 证据可追溯性
- 「相关能力识别」表格中的每一行是否都有「来源」？
- 业务现状描述是否有文档/代码依据？
- 是否存在无依据的猜测？
8. 一致性
- 术语使用是否前后一致？
- 需求描述是否有内部矛盾？
- 优先级标注是否合理？
9. Traceability Metadata
- 是否存在
TRACEABILITY-METADATAblock？ - 是否满足
prd-profile-v1？ - requirement、source document、derived_from 关系是否完整？
10. 1:N 拆分场景审查（当 PRD 属于 BRD 拆分场景时）
检测方式：检查 PRD 元信息是否包含「索引文档」或「关联 PRD」字段
如果 PRD 属于 1:N 拆分场景，必须检查：
索引文档验证
- 索引文档（PRD-INDEX-xxx.md）是否存在？
- 索引文档中是否包含「BRD 需求覆盖矩阵」？
- 覆盖率是否 = 100%？
- 本 PRD 是否被正确列入索引？
覆盖范围验证
- 本 PRD 的「覆盖范围」是否清晰定义？
- 与关联 PRD 是否存在需求重叠？（不应重叠）
- 与关联 PRD 是否存在需求遗漏？（不应遗漏）
跨 PRD 依赖验证
- 是否声明了与关联 PRD 的依赖关系？
- 依赖的协调方式是否明确？
问题分级
| 级别 | 名称 | 定义 | 处理方式 |
|---|---|---|---|
| P0 | 阻塞 | 必须修复才能准出 | 不放行，要求修改 |
| P1 | 严重 | 强烈建议修复 | 累计 ≥2 个不放行 |
| P2 | 建议 | 可以后续优化 | 记录，不阻塞放行 |
P0 阻塞问题示例
- 缺少必填章节（如验收标准、成功指标）
- 成功指标无法量化或缺少数据来源
- 需求存在内部矛盾
- 越界到 HLD 领域（包含 API 路径、数据库表结构等）
- 关键业务规则缺失
- 「相关能力识别」无来源依据
- 缺少
TRACEABILITY-METADATAblock，或 block 无法解析 schema.profile不是prd-profile-v1- requirement 缺少稳定
REQ-*或缺少acceptance_criteria - [1:N 场景] 索引文档不存在
- [1:N 场景] BRD 需求覆盖率 < 100%（存在未分配需求）
What ships with it
6 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.
- 11d ago First seen · 237 lines · 54 tokens per session scan A e72c7bc07a76
prd-reviewer is a skill published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 2,723 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…