AC dev-workflow
结构化开发工作流，强制执行 Plan → Implement → Review 流程。 触发条件： (1) 用户输入 KAIFA## 命令 (2) 自然语言包含开发类关键词："开发"+"SKILL/APP/应用/系统/模块/功能/工具"、"实现"+"功能/模块"、"写"+"模块/系统/服务"、"重构"、"新建"+"项目/模块" (3) 不确定时反问用户确认 不触发：简单单文件修改、配置更新、查询类请求、小bug修复 支持多角色子 agent 协作（Architect/Developer/Reviewer），自动按复杂度分配模型（pro=深度推理，flash=确定性执行），产出的 Plan 和 Review 归档到 plans/ 目录。
As a process C 54/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: 6. 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 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (dev-workflow) differs from the folder (kaifaskillfz01)
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 45 steps
- 100Execution cost. Instruction body is 1359 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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 2 example trigger phrases
- +3Description length 321: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.