Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/spec
Write a feature spec — the "what & why" of a Kandev product feature, before coding.
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 13 more in the full report
14 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to find any existing specification documents across the repository that mention 'invoice-generation'. What specific script command should we execute?
| Checked | Without skill | With skill |
|---|---|---|
| Runs python3 scripts/list-docs.py specs with --text invoice-generation and --format paths. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to create or update durable specifications. Requirements define observable behavior. System designs define the technical path that satisfies requirements.
The canonical rules are in docs/specs/guide/. Read these files before you
write an artifact:
structure-and-ownership.md.requirements.md for requirement work.system-design.md for system-design work.traceability-and-lifecycle.md for IDs, statuses, references, or
migration work.Use the templates in docs/specs/templates/.
Route the request before you write:
| Request | Artifact |
|---|---|
| Kandev-wide purpose, actors, principles, measures, or constraints | docs/specs/product/ |
| Observable behavior for one owning system | <system>/requirements/ |
| Technical contracts, models, boundaries, or control flow | <system>/system-design/ |
| Durable choice with meaningful alternatives | /record and an ADR |
| Delivery sequence and implementation tasks | /plan |
| Incident or behavior-preserving refactor | No product requirement |
| Bug | /fix, which checks the existing requirement first |
Do not create a generic spec.md file.
When routing to docs/specs/product/, read docs/specs/product/README.md
before editing. Treat its Product document index as the local index: read
every linked product document and any co-located INDEX.md, AGENTS.md,
CLAUDE.md, or other instruction file when present. Product files provide
cross-system context, not feature requirements; preserve proposed and
open-question language instead of promoting it to an active contract without
confirmation.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.