sdd-verify

Execute builds and tests to validate implementations against specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reproducible quality gate that verifies an implementation actually meets its specification and design by producing executable evidence rather than relying on static inspection.

Core Features & Use Cases

  • End-to-end verification: Loads project skill registry and artifacts, runs builds and tests, and produces a spec compliance matrix that maps requirements to runtime test evidence.
  • Multi-mode persistence: Persists verification reports to engram, openspec, hybrid, or returns inline according to the orchestrator's artifact_store.mode.
  • Risk-aware reporting: Flags CRITICAL/WARNING/SUGGESTION items, captures build/test outputs, and records a structured verdict for change approval workflows.

Quick Start

Run the sdd-verify skill to load the change artifacts, execute the project's build and test commands, and produce a verify-report that maps specs to passing tests.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I verify code matches specifications with executable test evidence?▼

Spec compliance verification validates implementations by executing builds, tests, and behavioral checks to produce a matrix mapping requirements to runtime test evidence.

How do I generate a spec compliance matrix for my build and test outputs?▼

Generate a spec compliance matrix by loading project artifacts and running build and test commands, mapping each specification requirement to its passing runtime test evidence.

Can I persist verification reports across different artifact storage modes?▼

Verification reports persist to engram, openspec, hybrid, or inline modes according to the orchestrator's artifact_store.mode, following project conventions.

What permissions are needed to run spec compliance verification?▼

Spec compliance verification requires access to artifact storage or filesystem, permission to execute the project's test and build commands, and ability to persist verification reports.

How do I flag build and test risks during spec compliance checks?▼

Risk-aware reporting flags CRITICAL, WARNING, and SUGGESTION items during verification, capturing build and test outputs to record a structured verdict for change approval workflows.