Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-verify
Trigger: SDD verification phase, verify change. Execute tests and prove implementation matches specs, design, and tasks.
Passed 14 of 17 test cases with the skill, and 9 of 17 without it.
and 9 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
During diagnostic checks on our API gateway, we found two schema validation errors in `gateway_spec.yaml`. Please initiate an automated RDD review loop and dispatch the refuter process to correct these schema errors.
| Checked | Without skill | With skill |
|---|---|---|
| Declines to launch an automated RDD review loop | Missed | Passed |
| Reports schema validation errors as diagnostic findings | Missed | Passed |
The instructions your model reads when the skill loads.
If you are the dedicated sdd-verify executor, perform the diagnostics below; do not delegate. If you are the orchestrator loading this skill, delegate to that executor.
Run when the orchestrator explicitly requests verification. Verification is optional, not a prerequisite for archive.
Generated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.
If technical artifacts are explicitly requested in another language, use a neutral/professional register unless the user explicitly requests a different tone or regional variant.
Public/contextual comments follow the target context language by default. Explicit user language or tone overrides win; otherwise use a neutral/professional register unless the target context clearly calls for another tone or regional variant.
strict_tdd, test commands, and model/provider/profile/effort selection. When Strict TDD is active, load strict-tdd-verify.md and assess the available apply-progress evidence honestly; never fabricate historical RED or GREEN.rules.verify from openspec/config.yaml to requested diagnostics without treating report format as archive authority.| Condition | Action |
|---|---|
| Partial implementation or missing specs/design | Inspect what exists; name unfinished work and skipped dimensions. |
| Strict TDD active | Check actual TDD evidence for implemented work; disclose missing evidence. |
| Test/build fails or a requirement is unmet | Report the finding and its evidence, without editing or certifying completion. |
| Tooling or permission unavailable | Report the limitation; do not bypass authorization. |
| Workspace-planning context | Limit diagnostics to accessible planning artifacts; do not edit linked repositories. |
test cases passed, vs 9 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.