AF build-planner
When the user wants to generate a development plan, choose a tech stack, break down features into tasks, or get a step-by-step build roadmap for their website or Mini Program MVP. Also use when the user mentions "开发计划", "技术选型", "roadmap", "怎么开发", "development plan", "tech stack", "build roadmap", "task breakdown". For defining what to build first, see product-scoper. For finding opportunities, see opportunity-finder.
When the user wants to generate a development plan, choose a tech stack, break down features into tasks, or get a step-by-step build roadmap for their website…
As a process F 57/100 · Will not run — References files that are not bundled: ../../examples/build-plan.md
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../examples/build-plan.md
Process rating: all ten parameters 57/100
- 0Tools and files. 1 referenced file(s) missing: ../../examples/build-plan.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (build-planner) differs from the folder (niche-build-planner)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Steps. 6 steps
- 100Execution cost. Instruction body is 1093 tokens
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 420: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.