BF pm-requirement
PM 需求产出 skill。引导 PM 从命题到可提交 review 的 PRD v1.0 完整走一遍,融合通用 PRD 规范 + MVP 分享的三步对话法 + 4 步推进 + 门禁机制。支持 0→1 新项目和迭代需求两种模式。触发场景:用户说"写 PRD"、"做需求"、"启动新项目需求"、或 workflow-start 路由到此 skill。
PM 需求产出 skill。引导 PM 从命题到可提交 review 的 PRD v1.0 完整走一遍,融合通用 PRD 规范 + MVP 分享的三步对话法 + 4 步推进 + 门禁机制。支持 0→1 新项目和迭代需求两种模式。触发场景:用户说"写 PRD"、"做需求"、"启动新项目需求"、或…
As a process F 36/100 · Will not run — References files that are not bundled: templates/project-versions.md, templates/prd-template.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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
missing-refreference to a missing file: templates/project-versions.md - warning
missing-refreference to a missing file: templates/prd-template.md
Process rating: all ten parameters 36/100
- 0Tools and files. 2 referenced file(s) missing: templates/project-versions.md, templates/prd-template.md
- 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
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (pm-requirement) differs from the folder (workflow-dlc-pm-requirement)
- 100Steps. 97 steps
- 100Execution cost. Instruction body is 2062 tokens
- 100Running it twice. No mutating operations
- low 10 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
- -256 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 174: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 97 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.