skills.rest
CarlosWilliamsR
CarlosWilliamsRCOMMUNITY
Explore all skills by this author →
GitHub

sdd-verify

Verify SDD change implementations by executing tests and comparing results against specs, design, and tasks.

Updated Aug 25, 2026
Search Tags:#testing#tdd#verification#quality gate#sdd#spec-driven development#test execution
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-verify-carloswilliamsr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/sdd-verify
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-verify-carloswilliamsr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It closes the gap between claimed implementation and proven behavior in spec-driven development by requiring real test execution evidence before a change can be marked complete. ## Core Features & Use Cases - Runtime Verification: Executes test, build, and coverage commands and records exit codes and output hashes as evidence. - Spec Compliance Matrix: Maps every requirement and scenario to a covering test with COMPLIANT, FAILING, UNTESTED, or PARTIAL status. - Strict TDD Auditing: Optionally validates RED/GREEN cycle evidence, assertion quality, test layer distribution, and changed-file coverage. - Use Case: After an apply phase finishes a change, run verification to produce a PASS, PASS WITH WARNINGS, or FAIL verdict with a persisted verify-report before settlement. ## Quick Start Ask the orchestrator to run the SDD verification phase for the current change and return the verification report with its final verdict.

Frequently Asked Questions about sdd-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an SDD change implementation?▼

Run the verification phase after all tasks are complete. It reads the proposal, specs, design, and tasks, executes the test and build commands, maps each spec scenario to a passing covering test, and returns a PASS, PASS WITH WARNINGS, or FAIL verdict.

What is Strict TDD verification in spec-driven development?▼

Strict TDD verification validates that the apply phase actually followed test-driven development. It checks the TDD Cycle Evidence table, confirms reported tests exist and pass, audits assertion quality for tautologies, and reports changed-file coverage.

Can verification pass with only a tasks artifact and no specs?▼

Yes, but only for task completion. With tasks only, it verifies objective completion and may return PASS WITH WARNINGS; it never claims spec correctness or design coherence without those artifacts.

Why does verification return blocked instead of running tests?▼

Verification returns blocked when any task is still incomplete. Full verification only runs after all tasks are checked off; pending tasks are treated as CRITICAL findings.

Does static code analysis count as verification?▼

No. Static analysis alone is never verification. A spec scenario is compliant only when a covering test passed at runtime, and test/build exit codes plus output hashes must be recorded in the report envelope.

Related Skills

Explore More Software Engineering Skills→
Gentleman-ProgrammingGentleman-Programming
6.1k

sdd-onboard

Guides users through a complete Spec-Driven Development cycle on their real codebase.

Official
Advanced
goerngoern
113

openspec-verify-change

Verify implementation matches delta specs, tasks, and design artifacts.

Community
Advanced
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
6.1k

sdd-archive

Archives completed SDD changes by syncing delta specs into main specs and moving change folders.

Official
Advanced