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 agentmods add skills/pieable/dragon-ball-agent/product-developmentnpx skills add pieable/dragon-ball-agent --skill product-developmentgit clone --depth 1 https://github.com/pieable/dragon-ball-agentWrote 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/pieable/dragon-ball-agent/product-development)<a href="https://agentmods.dev/skills/pieable/dragon-ball-agent/product-development"><img src="https://agentmods.dev/badge/skills/pieable/dragon-ball-agent/product-development.svg" alt="Measured on agentmods" 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 | $0.00102 | $0.02032 |
| Opus 5 | $0.00051 | $0.01016 |
| Sonnet 5 | $0.00020 | $0.00406 |
| Haiku 4.5 | $0.00010 | $0.00203 |
Grade A, and why
product-development 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
产品开发
以这条循环作为产品开发的基准:
倾听客户
→ 定义问题
→ 发明解决方案
→ 完善解决方案
→ 测试并迭代
循环表达的是一套连贯判断,不是必须按顺序走完的瀑布流程。测试、新证据和实现中的发现可以让工作回到任何较早阶段。其他产品方法只是在当前环节存在具体未知时可以选择的工具,不增加新的主流程,也不把不同公司的完整制度拼接起来。
产品观
客户持续追求更好的结果,却未必能够说出理想产品的形态。倾听客户是理解其现实、愿望和判断,不是让客户替团队设计功能。产品团队负责代表客户解释这些材料,结合技术与环境中正在出现的新可能,提出一个比现状更接近理想的具体产品。真实选择、使用行为和结果负责检验这项定义。
这里的“客户”按产品实际关系理解,可以是直接使用者、购买者、操作者或会受到产品影响的人。先确定谁的结果决定产品价值,不把最容易接触到的意见自动当作客户现实。
与客户共同形成决定
产品定义早期需要通过对话补足客户现实时,优先使用开放问题,让客户描述具体经历、愿望、判断和不能接受的结果。此时没有形成可靠的整体理解或真正不同的产品路线,就不要把零散概念提前压成选项,也不要让客户在看不到全局时替团队决定架构。
证据已经足以形成少量本质不同的路线时,先说明当前问题全景、各路线处于哪个共同层级、会改变什么以及团队的当前倾向,再请当前用户或明确的产品责任人决定只有他们能够决定的价值取舍。候选必须比较同一维度上的真实选择。整体架构、数据表达和局部策略等不同层级的概念不能伪装成互斥选项。
客户提供现实、反应和结果证据。当前用户或明确的产品责任人决定会实质改变客户价值、整体体验、目标范围、成本、长期维护、权限、外部影响或严重后果的取舍。可从产品、代码或环境取得的事实由团队主动调查。普通、可逆且不改变上述结果的实现细节由团队自行判断并连续推进。
开放表达告一段落,剩余问题已经能够形成边界清楚、同层级而且可以直接比较的选择时,比较切换 Plan mode 和直接回复的实际操作成本。选择控件能让用户更省力地理解或表达决定时,说明原因并建议开启 Plan mode。候选数量本身不构成触发条件。仍需自由表达、简单确认或直接回复数字和短句更方便时,继续使用普通对话。Plan mode 不提供另一套产品规划方法。进入后继续沿用本 Skill 当前的产品开发判断,并允许用户改写问题或给出未列答案。
推进粒度服从风险、依赖、可逆性和客户影响。避免用一份一次性总计划掩盖尚未设计的内容,也不把反对 one-shot 变成固定阶段、固定模板或逐项请示。复杂工作只在有助于理解和控制时保留整体方向、当前已展开部分和下一处关键决定。简单任务与不需要客户介入的细节由团队自行拆解、实施和验证。
运行循环
倾听客户
先利用已有的一手材料。现有证据不足以支撑判断时,再取得会改变产品定义的证据。优先让客户还原最近一次真实发生的相关情景:什么触发了事情、当时想完成什么、实际怎样行动、借助了哪些替代办法、在哪里犹豫或受阻、付出了什么代价、最后得到什么结果。能观察实际环境和行为时,不只询问偏好与满意度。
把客户原话和可观察事实同团队的解释、推断与假设分开。无法接触真实客户时,可以使用现有产品行为、支持记录、市场材料和可靠研究形成暂定理解,但要保留证据边界,不把推测写成已验证需求。
定义问题
把材料收束成团队真正要改变的处境:谁在什么情境下试图取得什么进展,当前方式为何不足,这造成什么后果,为什么值得现在解决。问题定义应受到证据、业务目的和现实约束支持,同时给不同解法留下空间。如果它已经暗含某个界面或功能,就继续追问其背后的结果。
确认看到的是客户完整任务,而不是组织内部的一小段流程或单个症状。证据改变了问题时,直接重写定义,不保护最初说法。
发明解决方案
由产品团队定义产品形态。以客户获得更好结果的完整未来经历为对象,说明产品怎样介入、关键转变由什么机制发生、最后为什么明显优于现状,不用功能数量代替产品概念。
当前方向可能只是第一个熟悉答案时,探索本质不同的产品定义,尤其检查新技术、领先用户的做法、环境变化或产品意义的改变是否允许取消旧产品中看似理所当然的限制。探索以形成真正不同的选择为止,不为展示发散数量制造相似方案。
完善解决方案
把概念具体到另一个不了解本次对话的设计者或开发者能够还原产品愿景,又不给尚未决定的低层实现制造虚假确定性。根据需要使用未来叙事、PR/FAQ、场景图、交互骨架或可运行片段,使团队能够沿客户的端到端经历慢速走查,发现缺失步骤、相互依赖、错误假设和难以实现的部分。
完善不是不断增加功能,而是在目标投入内解决会使产品失效的关键问题,并明确范围、约束和有意不做的内容。普通且可逆的细节交给实施者判断。会改变客户价值、整体体验、可实现性或产生严重后果的部分应在投入实现前说清或验证。
What ships with it
20 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.
- agents/openai.yaml 295 B
- references/define/evidence-synthesis.md 1.2 KB
- references/define/problem-reframing.md 1.1 KB
- references/define/working-backwards-questions.md 1.1 KB
- references/invent/alternative-product-worlds.md 1.2 KB
- references/invent/analogous-inspiration.md 889 B
- references/invent/co-creation.md 936 B
- references/invent/future-experience-narrative.md 1.2 KB
- references/listen/contextual-observation.md 1.1 KB
- references/listen/journey-reconstruction.md 1.1 KB
- references/listen/lead-user-research.md 1.0 KB
- references/listen/recent-situation-interview.md 1.3 KB
- references/refine/appetite-and-boundaries.md 1.0 KB
- references/refine/end-to-end-walkthrough.md 1.2 KB
- references/refine/pr-faq.md 1.1 KB
- references/refine/risk-review.md 1.1 KB
- references/test/experiment-selection.md 1.2 KB
- references/test/test-and-iteration.md 1.2 KB
- references/toolbox.md 2.4 KB
- RULE_RATIONALE.md 9.5 KB
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.
- 4d ago First seen · 81 lines · 102 tokens per session scan A 79fbbf19f13d
product-development is a skill published in the GitHub repository pieable/dragon-ball-agent (11 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 2,032 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…