BD pm-requirement-sharpening-stone
帮助 PM 在需求启动阶段,通过三步对话法(苏格拉底→第一性→奥卡姆)拆清问题本质, 产出可进 review 的 PRD v3.x 终稿。支持按需裁剪章节、按需启用场景定位/Agent 设计/学习循环等可选阶段。 输出优先飞书文档,降级本地 MD。
帮助 PM 在需求启动阶段,通过三步对话法(苏格拉底→第一性→奥卡姆)拆清问题本质, 产出可进 review 的 PRD v3.x 终稿。支持按需裁剪章节、按需启用场景定位/Agent 设计/学习循环等可选阶段。 输出优先飞书文档,降级本地 MD。
As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5039 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "name_zh" - note
frontmatter-keyunknown frontmatter key "scope" - note
frontmatter-keyunknown frontmatter key "not_for" - note
frontmatter-keyunknown frontmatter key "examples"
Process rating: all ten parameters 40/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (pm-requirement-sharpening-stone) differs from the folder (requirement-sharpening-stone)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5039 tokens
- 100Steps. 183 steps
- 100Running it twice. No mutating operations
- low 21 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2128 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 124: enough signal without eating the budget
- +4Structure: 74 headings
- +3Step-by-step instructions: 183 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: clean
This PRD workflow skill is purpose-aligned and disclosed, but users should be aware it can create Feishu documents, use web search, read local project context, and write local process logs.
LLM: benign (medium) · VirusTotal: · 25 Jun 2026