sdd-verify

Validate SDD changes against specifications and designs with test evidence.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill sdd-verify-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-verify
Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-verify-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the risk of deploying SDD (spec/design/task) changes that only look correct on paper by enforcing verification against specs with runtime test proof.

Core Features & Use Cases

  • Spec-to-implementation verification: Maps each spec requirement/scenario to implementation evidence and runtime test outcomes.
  • Test execution as the compliance gate: Requires relevant tests to run and treats non-zero exits as critical verification failures.
  • Strict TDD protocol auditing (optional module): When Strict TDD is enabled and a runner exists, validates that apply-phase TDD evidence matches reality.
  • Structured verification reporting: Produces a comprehensive Verification Report including completeness tables, evidence, compliance matrix, and categorized issues.

Quick Start

Ask the orchestrator to run the SDD verification phase for your change so the skill executes tests, validates spec compliance, 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 spec compliance for software changes using test execution?

Spec compliance verification maps each requirement to implementation evidence and executes covering tests, treating non-zero exits as critical failures to ensure changes match their specifications at runtime.

What is SDD verification and how does it validate design changes?

SDD validation confirms that spec, design, and task changes look correct at runtime by collecting build evidence, running covering tests, and producing a structured verification report with compliance matrices.

How do I generate a verification report with categorized issues for test evidence?

Generate a verification report by executing covering tests and mapping outcomes to spec requirements, which produces completeness tables, evidence, compliance matrices, and categorized CRITICAL, WARNING, and SUGGESTION issues.

Does spec compliance verification support strict TDD protocol auditing?

Yes, when strict TDD is enabled, the verification process optionally audits apply-phase TDD evidence against reality to validate that test-driven development protocols match implementation outcomes.

Can I use test execution as a quality gate for requirement compliance mapping?

Yes, test execution acts as the compliance gate by requiring relevant tests to run and mapping scenario-to-test compliance, returning a shared SDD phase envelope with build, test, and coverage evidence.

Why does spec verification fail when test execution returns a non-zero exit code?

Spec verification fails because non-zero test exits are categorized as critical verification failures, ensuring that runtime test proof validates spec compliance and preventing changes that only look correct on paper.