BD mu-dev-workflow
软件开发工作流+通用方案输出自检，融合Superpowers方法论，强制设计先行→批判性三问自检→计划分解→子Agent执行→双阶段Review。触发词：开发、写代码、新功能、新skill、重构、修bug、实现、build、implement、帮我做一个、方案自检、三问自检。即使用户没有明说"走流程"，只要涉及新建/修改/重构代码或Skill，就应触发。不适用：纯闲聊。
软件开发工作流+通用方案输出自检，融合Superpowers方法论，强制设计先行→批判性三问自检→计划分解→子Agent执行→双阶段Review。触发词：开发、写代码、新功能、新skill、重构、修bug、实现、build、implement、帮我做一个、方案自检、三问自检。即使用户没有明说"走流程"，只要涉及新建/…
As a process D 45/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.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 4, column 162: …ild、implement、帮我做一个、方案自检、三问自检。即使用户没有明说"走流程"，只要涉及新建/修改/重构代码或Skill，就应触发。不适用：纯闲聊。" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "paths"
Process rating: all ten parameters 45/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1790 tokens
- 100Progress reporting. Reports progress
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
- -215 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 186: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.