sdd-verify

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-verify-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-verify
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-verify-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated code often claims completion without proof. This Skill acts as the quality gate for the Spec-Driven Development verification phase, proving that an implementation actually matches its specs, design, and task list through real test execution rather than static inspection alone. ## Core Features & Use Cases - Runtime Verification: Executes test, build, and coverage commands and maps every spec scenario to a passing covering test, producing a compliance matrix with COMPLIANT, FAILING, UNTESTED, or PARTIAL statuses. - Strict TDD Auditing: When Strict TDD mode is active, validates the RED-GREEN-REFACTOR evidence from the apply phase, audits assertion quality (tautologies, ghost loops, smoke tests), classifies test layers, and measures changed-file coverage. - Graceful Degradation: Adapts verification depth to available artifacts — tasks only, tasks plus specs, or full proposal/specs/design/tasks — and records skipped dimensions explicitly. - Use Case: After an SDD apply phase finishes a change, the orchestrator delegates to this Skill, which runs the test suite, cross-checks spec scenarios against results, and returns a verdict of PASS, PASS WITH WARNINGS, or FAIL with issues grouped by severity. ## Quick Start Ask the orchestrator to run the SDD verification phase for the current change so it delegates to the sdd-verify sub-agent and returns a verification report.

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 against its specs?▼

Run the SDD verification phase, which delegates to the sdd-verify sub-agent. It reads the proposal, specs, design, and tasks, executes the test suite, and maps each spec scenario to a passing covering test before issuing a PASS, PASS WITH WARNINGS, or FAIL verdict.

What does the SDD verification report contain?▼

The report includes task completeness counts, build and test execution evidence, a spec compliance matrix with COMPLIANT, FAILING, UNTESTED, or PARTIAL statuses, design coherence checks, and issues grouped as CRITICAL, WARNING, or SUGGESTION.

Does sdd-verify support strict TDD workflows?▼

Yes. When Strict TDD mode is active and a test runner exists, it loads the strict-tdd-verify module to audit RED-GREEN-REFACTOR evidence, classify test layers, measure changed-file coverage, and flag trivial assertions like tautologies or ghost loops.

Can verification run when only the tasks artifact exists?▼

Yes, it degrades gracefully. With tasks only, it verifies objective task completion and skips spec correctness and design coherence, recording the skipped dimensions. Unchecked implementation tasks remain CRITICAL regardless.

Why does verification fail even when the code looks correct?▼

Static inspection alone never counts as verification. A spec scenario is compliant only when a covering test passed at runtime, so missing or failing tests produce CRITICAL UNTESTED or FAILING findings even if the source code appears correct.