AC spec-flow
轻量级 SDD（规范驱动开发）文档流水线。当用户描述一个新功能、产品想法或改进需求， 希望在动手写代码前先把"做什么/为什么/怎么做/拆成哪些任务"梳理清楚时使用。 自动完成 constitution → spec → plan → tasks 全流程，产出对齐 GitHub spec-kit 的 .specify/ 目录。 触发："我想加一个 XX 功能""帮我规划/设计 XX""这个需求先出个开发文档"。 不触发：纯代码实现、bug 修复、已有 spec 的局部修改、多智能体编排（那属于完整版 Harness 场景）。
轻量级 SDD（规范驱动开发）文档流水线。当用户描述一个新功能、产品想法或改进需求， 希望在动手写代码前先把"做什么/为什么/怎么做/拆成哪些任务"梳理清楚时使用。 自动完成 constitution → spec → plan → tasks 全流程，产出对齐 GitHub spec-kit 的…
As a process C 53/100 · Has gaps — 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: 7. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 606 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 264: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.