CD flow-elaboration-to-construction
Orchestrate Elaboration→Construction phase transition with iteration planning, team scaling, and full-scale development kickoff
Orchestrate Elaboration→Construction phase transition with iteration planning, team scaling, and full-scale development kickoff
As a process D 47/100 · Unfinished process — References files that are not bundled: templates/management/iteration-plan-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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. 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
body-longSKILL.md body ≈ 7590 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: templates/management/iteration-plan-template.md - note
frontmatter-keyunknown frontmatter key "namespace" - note
frontmatter-keyunknown frontmatter key "commandHint"
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: templates/management/iteration-plan-template.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 7590 tokens
- 100Steps. 79 steps
- 100Consistency. Name and required fields are in place
- low 12 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
- +1No license
- +2Single-language instructions
- +3Description length 127: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 79 items
- +4Has examples (27 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.