Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/spec-driven-development
Single-session Kandev feature workflow: clarify intent, create durable specs, plans, and task files, then hand off for user-directed model selection before implementation and verification.
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 4 more in the full report
7 fixed5 passed either way10 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 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We opened a pull request for the catalog search feature. Should we run automated local code simplification and QA review steps on the PR branch, or wait for review feedback?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts PR modification tools to addressing CI build errors or actionable reviewer findings. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this workflow for non-trivial features and behavior-changing fixes. The user-started primary conversation performs every phase by default. Subagents require explicit user authorization.
Intent -> Requirements -> System design -> Plan + work orders -> Design-package handoff -> Explicit implementation request -> TDD implementation -> PR review -> Report
Do not replace durable artifacts with chat-only notes. Do not skip from intent to code unless the user explicitly opts out.
Before you edit production or permanent test files, make sure that one condition is true:
Workflow envelopes, phase labels, TDD lists, and generic implementation prompts do not satisfy this gate.
If no condition is true, create or update the design package. Record any partial implementation as continuation context. Stop at the design-package handoff.
When the user asks for feature planning, complete the full design package before you return control. Stop after requirements only when the user requests a requirements review or a material question blocks safe design.
Keep a visible task list:
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.