BF prd-implementation-ready
Use when writing, reviewing, or filling gaps in PRDs, product requirements, BRDs, functional specs, or SaaS/admin workflows that must become implementation-ready. Especially useful for business flows, object states, page UX, data sources, permissions, exceptions, finance/payment/reconciliation/profit-sharing, formulas, and post-event writebacks.
Especially useful for business flows, object states, page UX, data sources, permissions, exceptions, finance/payment/reconciliation/profit-sharing, formulas…
As a process F 51/100 · Will not run — References files that are not bundled: references/research-and-flow.md, references/page-ui.md, references/stage-gates.md
How to improve
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9138 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/research-and-flow.md - warning
missing-refreference to a missing file: references/page-ui.md - warning
missing-refreference to a missing file: references/stage-gates.md - warning
missing-refreference to a missing file: references/necessity-gate.md - warning
missing-refreference to a missing file: references/business-anchors.md - warning
missing-refreference to a missing file: references/business-context.md - warning
missing-refreference to a missing file: references/coverage-matrix.md - warning
missing-refreference to a missing file: references/data-flow.md - warning
missing-refreference to a missing file: references/business-consistency.md - warning
missing-refreference to a missing file: references/finance-operations.md - warning
missing-refreference to a missing file: references/review-checklists.md - warning
missing-refreference to a missing file: references/source-language-guards.md - warning
missing-refreference to a missing file: references/output-structure.md
Process rating: all ten parameters 51/100
- 0Tools and files. 13 referenced file(s) missing: references/research-and-flow.md, references/page-ui.md, references/stage-gates.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 9138 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 85Steps. 116 steps, 2 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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 347: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 116 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.