AB product-roadmap
Build and manage a product roadmap for a solopreneur business. Use when deciding what to build next, prioritizing features, planning product development over quarters, communicating plans to customers or stakeholders, or managing scope and expectations. Covers prioritization frameworks, roadmap structure, customer feedback integration, and saying no to feature requests. Trigger on "product roadmap", "what to build next", "feature prioritization", "roadmap planning", "product strategy", "feature requests".
As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 63 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2309 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 10 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
- +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
- +5Description quotes 6 example trigger phrases
- +3Description length 510: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.