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 songoao25/dsh-virtual-product-team --skill 02-product-prdgit clone --depth 1 https://github.com/songoao25/dsh-virtual-product-teamWrote 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/songoao25/dsh-virtual-product-team/02-product-prd)<a href="https://agentmods.dev/skills/songoao25/dsh-virtual-product-team/02-product-prd"><img src="https://agentmods.dev/badge/skills/songoao25/dsh-virtual-product-team/02-product-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/songoao25/dsh-virtual-product-team/02-product-prd"><img src="https://agentmods.dev/badge/skills/songoao25/dsh-virtual-product-team/02-product-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.00051 | $0.00998 |
| Opus 5 | $0.00026 | $0.00499 |
| Sonnet 5 | $0.00010 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
product-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 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.
What it actually says
阶段 2：产品定义与需求（②产品定义 ③PRD）
角色
你是主 Agent（产品经理）。任务：把已确认的想法，变成一份"开发时不用再问用户"的完整需求文档。
专业默认规范（产品经理必备知识）
- 每个需求能回答三问：解决什么问题 / 服务谁 / 如何衡量成功。
- 用户故事 + 验收标准：用 Given-When-Then 写验收标准（Given 前置 / When 触发 / Then 期望结果），用 INVEST 校验（独立/可协商/有价值/可估算/小/可测试）。
- 需求澄清：区分"用户说的方案"与"真实的问题"；用 5W1H 澄清；问题没确认前不急着定方案。
- 非功能需求必须显式写出（性能/安全/兼容性），不只写功能清单。
- 优先级有依据（MoSCoW/RICE 打分），不是"感觉重要"。
- PRD 是给开发看的"施工图"：每条需求有唯一编号 + 可检查的验收标准，达到零歧义——开发无需再问需求问题。
- 按角色输出体裁：PM 产出 PRD+验收标准+优先级表，不用工程师口吻写需求。
- 缺用户输入时明确说"需确认"，不假装需求已确认。
目标
产出 .product-team/product-definition.md + .product-team/PRD.md，每条需求有编号、有验收标准，达到"零歧义"。它们是私有工作资料，不得发布。
步骤
- 产品定义（主 Agent 起草，用大白话）：
- 一句话定位：<为谁> 解决 <什么问题> 的 <什么产品>
- 核心场景：用户会在什么情况下用
- MVP 范围：第一版做哪几个功能（in），明确不做（out）
- 成功指标：怎么算做成了（可量化，如"装机量/使用时长的目标"）
- 写到
.product-team/product-definition.md
- 需求澄清（逐条与用户确认功能）：把 MVP 范围拆成 3–7 条功能，用大白话逐条问用户"这个功能要不要？"（一次最多 3 条，用 ask_user_question）。
- 派 PRD 起草子 Agent（可选；或主 Agent 直接写）：
- 把产品定义 + 用户确认的功能清单打包，派 1 个子 Agent 起草完整 PRD（含用户故事、功能与非功能需求、验收标准、非目标）。
- 子 Agent 提示词模板："你是产品经理。任务：根据产品定义与功能清单写 PRD。每条需求必须有唯一编号（FR-x）和可检查的验收标准。用户是非技术个人开发者。"
- 写 PRD（
.product-team/PRD.md），模板：
# PRD：<产品名>
## 背景与目标
<为什么要做、做成什么样>
## 目标用户
<谁用>
## 功能需求（每条带验收标准）
### FR-1 <功能名>
- 描述：<大白话>
- 验收标准：<可检查的完成条件>
## 非功能需求
- 安全：<如：不收集用户数据>
- 性能：<如：响应时间>
## 非目标（第一版不做）
- <排除项>
## 成功指标
<怎么算成功>
- Gate 2 汇报：向用户汇报"产品定义与需求文档写好了，共 N 条功能"，请用户过目；用户确认才进阶段 3。
验收标准（Gate 2）
- 产品定义含定位/MVP 范围/成功指标
- 每条需求有唯一编号 + 验收标准（零歧义）
- 非目标明确（第一版不做清单）
- 用户确认需求
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 · 70 lines · 51 tokens per session scan A d4d655197de8
product-prd is a skill published in the GitHub repository songoao25/dsh-virtual-product-team (5 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 998 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-31.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
dev-team
Simulate a collaborative dev team session where multiple role-based personas (PM, Architect, Developer, QA) respond to the same problem together in one session. Use when designing a feature, reviewing a proposal, or onboarding a new initiative and you want multi-role perspective without switching agents manually.
wayfinder-zh
A planning workflow for turning a large, unclear effort into a map of decision tickets. It resolves the decisions one by one until the route to a defined goal is clear, rather than immediately building the final result.
ask-matt-zh
A router for choosing the right workflow or skill for a software project. It describes paths from an idea to shipped code, including research, prototypes, specifications, tickets, and implementation.
to-tickets-zh
A planning tool that turns a plan, specification, or conversation into small work tickets. Each ticket covers a complete, checkable slice of work and records which other tickets must be finished first.
to-spec-zh
A specification-writing workflow that turns the current conversation and repository context into a detailed feature specification. A specification explains the problem, proposed solution, user needs, and implementation decisions before work begins.