sdd-verify

Verifies SDD change implementations by executing tests and validating spec compliance.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/albersg/dotfiles --skill sdd-verify-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/sdd-verify
Command: npx skills add https://github.com/albersg/dotfiles --skill sdd-verify-albersg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It closes the gap between claimed implementation and proven correctness 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 from specs to a covering test with COMPLIANT, FAILING, UNTESTED, or PARTIAL status. - Strict TDD Auditing: Optionally validates TDD cycle evidence, test layer distribution, changed-file coverage, and assertion quality when Strict TDD mode is active. - Use Case: After an apply phase finishes an SDD change, the orchestrator delegates to this skill to run the test suite, compare results against specs and design, and produce a PASS, PASS WITH WARNINGS, or FAIL verdict report. ## 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?▼

Delegate to the sdd-verify sub-agent after all tasks are complete. It reads the proposal, specs, design, and tasks, runs the test and build commands, and returns a verification report with a PASS, PASS WITH WARNINGS, or FAIL verdict.

What does the SDD verification report contain?▼

The report includes a YAML evidence envelope, completeness table, build and test execution results, a spec compliance matrix mapping scenarios to tests, design coherence checks, issues grouped by severity, and a final verdict.

Does sdd-verify work when only a tasks artifact exists?▼

Yes, it degrades gracefully. With only tasks it verifies objective task completion and skips spec correctness and design coherence, recording the skipped dimensions in the report.

What happens if a test fails during SDD verification?▼

A non-zero test command exit is flagged as CRITICAL, and any spec scenario without a passing covering test is marked UNTESTED or FAILING. The skill only reports issues and never fixes them.

When is the Strict TDD verification module loaded?▼

It loads only when Strict TDD mode is active and a test runner is available. It then audits TDD cycle evidence, test layer distribution, changed-file coverage, and assertion quality such as tautologies and ghost loops.