BF fde-delivery-loop
An end-to-end delivery skill for Forward Deployed Engineers, solution architects, and enterprise AI POC teams. It combines one delivery router with eight independently runnable specialist modules to turn ambiguous customer needs into evidence, a POC charter, an acceptance-ready PRD, deployment architecture, an Agent Skill, POC evidence, adoption and value conclusions, and reusable delivery assets.
An end-to-end delivery skill for Forward Deployed Engineers, solution architects, and enterprise AI POC teams.
As a process F 53/100 · Will not run — References files that are not bundled: fde-problem-discovery/MODULE.md, fde-prd-writer/MODULE.md, fde-poc-runner/MODULE.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 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: 80. 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
missing-refreference to a missing file: fde-problem-discovery/MODULE.md - warning
missing-refreference to a missing file: fde-prd-writer/MODULE.md - warning
missing-refreference to a missing file: fde-poc-runner/MODULE.md - warning
missing-refreference to a missing file: scripts/project-state.js
Process rating: all ten parameters 53/100
- 0Tools and files. 4 referenced file(s) missing: fde-problem-discovery/MODULE.md, fde-prd-writer/MODULE.md, fde-poc-runner/MODULE.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 100Steps. 21 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1681 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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 400: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.