sdd-verify

Verify project changes against specs and save reports to OpenSpec paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that a completed or partial change conforms to the defined specs and design by executing the project's verification workflow and producing evidence reports.

Core Features & Use Cases

  • Load and execute verification steps across skills to validate completeness, correctness, and design coherence.
  • Generate audit-ready verify-reports and persist them under the openspec path for tracking changes.
  • Support governance by running tests, builds, and static checks to confirm alignment with specs.

Quick Start

Execute the verification workflow for the provided change to produce a verifiable 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 a code change against project specs and design?▼

Spec verification validates completed or partial code changes by executing the project's verification workflow to confirm alignment with defined specs and design, producing an audit-ready report.

What is the best way to generate audit-ready verification reports for software changes?▼

Audit-ready verification reports are generated by running tests, builds, and static checks, persisting the evidence under the openspec/changes/{change-name}/verify-report.md path for tracking.

How does OpenSpec spec-validation work for completed changes?▼

OpenSpec spec-validation works by applying retrieval, persistence, and compliance steps from the sdd-phase-common specification to load and execute verification workflows across coding tasks.

Can I run verification on partial code changes before a full build is complete?▼

Yes, spec verification supports partial changes by executing the verification workflow to validate completeness, correctness, and design coherence even when the project is not fully built.

Do I need OpenSpec conventions to run end-to-end change verification?▼

Yes, end-to-end change verification follows OpenSpec conventions, enforcing retrieval, persistence, and compliance steps while saving reports directly to the openspec directory structure.

Why does spec validation fail to produce a report for my coding task?▼

Spec validation requires the change to follow OpenSpec conventions, saving reports to openspec/changes/{change-name}/verify-report.md; missing compliance or failed static checks will halt report generation.