Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tencentblueking/tapd-product-discovery
Use when work starts before a complete PRD exists, including 产品前置, 产品调研, 用户调研, 竞品分析, PRD, 原型, 想法建单, 老板需求, 需求来源, 产品父单, 角色拆单, 设计子单, 前端子单, 后端子单, 页面原型 Spec, BKUI 原型, HTML 原型, 原型评审, product discovery, product research, PRD drafting, or role story split.
Passed 17 of 21 test cases with the skill, and 5 of 21 without it.
and 14 more in the full report
14 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
The product manager provided existing TAPD parent ticket ID #100888999 for workspace 200333 to continue product discovery. Which TAPD MCP API call and parameters should be used to inspect its current state?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes stories_get API call with workspace_id 200333 | Passed | Passed |
| Includes with_v_status set to '1' in the stories_get payload | Missed | Passed |
The instructions your model reads when the skill loads.
处理 PRD 之前的需求工作:想法记录、需求来源整理、用户调研、竞品分析、业务分析、PRD、页面原型 Spec、BKUI HTML 原型、原型评审和产品评审。流程从产品父单开始,按“想法记录 -> 产品调研 -> PRD -> 页面原型 Spec -> BKUI HTML 原型 -> 原型评审 -> 产品评审 -> 角色拆单”推进;产品方案通过后再按实际需要创建设计、前端、后端子单。
前端和后端子单创建后,继续使用已有研发流程处理;它不替代 tapd-story-clarification、tapd-story-evaluation、tapd-story-pipeline。
tapd-story-pipeline。tapd-story-clarification。tapd-story-evaluation。project.json 中存在 workspace_id。| 参数 | 来源 | 必需 | 说明 |
|---|---|---|---|
| 需求来源 | 用户输入 / TAPD 父单 | 是 | 想法、老板需求、用户反馈、竞品观察、已有草稿等 |
| 产品父单 ID | 用户输入 / 新建 | 否 | 已有父单则复用;没有则创建 |
| workspace_id | 用户输入 > project.json | 是 | TAPD 工作空间 ID |
| owner | 用户输入 > project.json | 否 | 产品负责人或当前处理人 |
| 背景知识 | 用户指定 > AGENTS.md 自动查找 | 否 | 业务说明、用户资料、竞品资料、架构约束、前后端规范等 |
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.