BF project-documentation
Complete workflow for project documentation including ADRs, PRDs, personas, and docs organization. Use when setting up documentation for a new project or improving existing docs. Triggers on project documentation, ADR, PRD, personas, docs structure, documentation setup.
As a process F 39/100 · Will not run — References files that are not bundled: ../../../commands/bootstrap/bootstrap-docs.md, ../../../commands/development/new-feature.md, ../../../agents/development/
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../commands/bootstrap/bootstrap-docs.md - warning
missing-refreference to a missing file: ../../../commands/development/new-feature.md - warning
missing-refreference to a missing file: ../../../agents/development/
Process rating: all ten parameters 39/100
- 0Tools and files. 3 referenced file(s) missing: ../../../commands/bootstrap/bootstrap-docs.md, ../../../commands/development/new-feature.md, ../../../agents/development/
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 4 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1157 tokens
- low 11 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 270: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.