BD evaluate-sdlc-layers
Validate and iterate on the SDLC Layer Separation Architecture implementation across the check categories defined in its Evaluation Checklist — cross-references, doc completeness, knowledge-explorer layer filters, research entry metadata, integration points, and plan consistency. Produces a structured findings report and optionally applies safe fixes. Use when validating a first-pass implementation, before claiming layer work complete, auditing layer docs or schema, or running --dry-run to preview findings without changes.
Validate and iterate on the SDLC Layer Separation Architecture implementation across the check categories defined in its Evaluation Checklist —…
As a process D 41/100 · Unfinished process — References files that are not bundled: ../../../plugins/development-harness/docs/sdlc-layers/, ../../../plugins/development-harness/skills/verify-done/SKILL.md, ../../../plugins/development-harness/skills/work-backlog-item/SKILL.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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../plugins/development-harness/docs/sdlc-layers/ - warning
missing-refreference to a missing file: ../../../plugins/development-harness/skills/verify-done/SKILL.md - warning
missing-refreference to a missing file: ../../../plugins/development-harness/skills/work-backlog-item/SKILL.md - warning
missing-refreference to a missing file: references/workflows/groom/start.md
Process rating: all ten parameters 41/100
- 0Tools and files. 4 referenced file(s) missing: ../../../plugins/development-harness/docs/sdlc-layers/, ../../../plugins/development-harness/skills/verify-done/SKILL.md, ../../../plugins/development-harness/skills/work-backlog-item/SKILL.md
- 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
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1245 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 528: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.