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 kelegele/oh-my-pm --skill clarify-requirementsgit clone --depth 1 https://github.com/kelegele/oh-my-pmWrote 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/kelegele/oh-my-pm/clarify-requirements)<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/clarify-requirements"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/clarify-requirements/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/kelegele/oh-my-pm/clarify-requirements"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/clarify-requirements.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.00110 | $0.04204 |
| Opus 5 | $0.00055 | $0.02102 |
| Sonnet 5 | $0.00022 | $0.00841 |
| Haiku 4.5 | $0.00011 | $0.00420 |
Grade A, and why
clarify-requirements 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 12d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify Requirements
Overview
在 PRD 生成前,确保所有感知数据已收集,且用户批准了内容方案。参考 superpowers brainstorming 的"逐步确认 → 方案审阅 → 用户批准"流程设计。
HARD GATE
在以下条件全部满足前,禁止调用 prd-gen 或任何 design 层 skill:
- 信息差距分析完成
- 每个缺失项已逐一向用户确认(一次一个问题)
- PRD 内容方案已呈现给用户
- 用户已明确批准方案
Anti-Pattern: "信息够了,直接生成吧"
禁止。即使你认为信息已经足够,也必须呈现方案并获得用户批准。"简单"需求更容易因为遗漏关键信息而导致 PRD 返工。
Evidence Discipline (证据纪律)
- 缺失信息标记【待确认】:任何无法从输入或上下文获得的信息,标记为【待确认】,不得脑补填默认值。
- 证据追溯【未验证】:用户需求/市场断言必须追问证据来源;无证据的标记为【未验证】并注明所需验证方式。
- 完整度检查门:正式输出交付物前,先输出信息完整度清单(已确认 ✅ / 待确认 ⚠️ / 未验证 ❓),经用户确认后才生成正文。
- 可追溯:正式输出中的关键结论必须能追溯到以下来源之一:已确认的用户输入、引用的证据(含 URL)、或用户的显式决策;无法追溯的结论视为脑补,删除或改标【待确认】。
对话规则
访谈式澄清遵守以下三条规则:
- 不复读:默认不逐条复述用户的回答,确认后直接推进下一个问题;仅在回答含糊、前后矛盾、或影响后续方案时,才复述关键信息向用户确认。
- 宽泛回答收敛:用户回答太宽泛时,给出 2-4 个具体选项帮用户收敛,不替用户做决定。
- 例:用户说"就是体验不好" → "具体是哪类体验问题?" → A. 操作步骤太多 B. 页面加载慢 C. 找不到想要的功能 D. 界面信息太乱
- 例:用户说"想优化一下后台" → "'优化'主要指什么?" → A. 减少重复录入 B. 报表更直观 C. 审批流程更短 D. 移动端可用
- 每阶段具体问法:围绕背景触发 / 用户场景 / 问题证据 / 目标指标四个维度提问,避免空泛的"还有什么要补充的吗":
- 背景触发:"是什么触发了你现在提这个需求?" / "这个问题存在多久了?"
- 用户场景:"谁在什么场景下会遇到这个问题?现在是怎么解决的?"
- 问题证据:"有什么证据表明这个问题存在?"(数据、用户反馈、工单记录均可;无证据按证据纪律标【未验证】)
- 目标指标:"做成什么样算解决了?哪个指标会变化、基线是多少?"
Process Flow
digraph clarify {
"Explore context" [shape=box];
"Gap analysis" [shape=box];
"Ask one question at a time" [shape=box];
"Handle missing assets" [shape=box];
"Generate PRD plan" [shape=box];
"Present plan to user" [shape=box];
"User approves?" [shape=diamond];
"Save clarification result" [shape=box];
"Proceed to PRD generation" [shape=doublecircle];
"Explore context" -> "Gap analysis";
"Gap analysis" -> "Ask one question at a time";
"Ask one question at a time" -> "Handle missing assets";
"Handle missing assets" -> "Generate PRD plan";
"Generate PRD plan" -> "Present plan to user";
"Present plan to user" -> "User approves?";
"User approves?" -> "Generate PRD plan" [label="no, revise"];
"User approves?" -> "Save clarification result" [label="yes"];
"Save clarification result" -> "Proceed to PRD generation";
}
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.
- 12d ago First seen · 287 lines · 110 tokens per session scan A 2d37fea90261
clarify-requirements is a skill published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 4,204 once invoked, about $0.0006 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
clean-code
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a…