sdd-verify

Identifies non-conformances in implemented OpenSpec changes and outputs a verify-report.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fearovex/claude-config --skill sdd-verify-fearovex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/fearovex/claude-config/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/fearovex/claude-config --skill sdd-verify-fearovex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that software changes conform to the defined specifications, design artifacts, and task plans, generating a centralized verify-report that documents compliance.

Core Features & Use Cases

  • Completeness Check: compare planned tasks against implemented changes and report any missing or incomplete items.
  • Correctness Check: assess each Given/When/Then scenario across specs to ensure coverage in code and tests.
  • Coherence Check: validate that the implemented design decisions align with the intended architecture and constraints.
  • Testing & Reporting: attempt to run the project's tests if present and embed results into verify-report; otherwise rely on static code evidence.
  • Artifact Generation: produce openspec/changes/<change-name>/verify-report.md summarizing the findings.
  • Workflow Integration: reads openspec/changes/<change-name>/tasks.md, specs/, design.md, and code to perform analysis.

Quick Start

Trigger the verification by specifying the <change-name> and running the sdd-verify workflow to generate openspec/changes/<change-name>/verify-report.md

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I verify implemented code against specifications and design artifacts?

You can verify code against specifications by running a verification workflow that compares implemented changes against tasks.md, specs/, and design.md. It outputs a verify-report documenting compliance, completeness, and coherence without modifying the source code.

What is change verification in software engineering?

Change verification validates that code implementations conform to defined specifications, design artifacts, and task plans. It enforces completeness, correctness, coherence, and testing checks to ensure reliable software releases.

How do I check if my code changes cover all Given/When/Then scenarios?

To check Given/When/Then scenario coverage, apply a correctness check that assesses each scenario across specs to ensure coverage exists in code and tests. The findings are compiled into a centralized verify-report.

Can I validate task completeness for changes tracked under openspec/changes?

Yes, you can validate task completeness for openspec/changes by comparing planned tasks against implemented changes. The completeness check identifies and reports any missing or incomplete items in the generated verify-report.

Does the verification process run project tests automatically?

The verification process attempts to run the project's tests if present and embeds the results into the verify-report. If no tests are available, it relies on static code evidence to assess compliance.

What are the limitations of using static code evidence for change verification?

When relying on static code evidence for change verification, the limitation is that actual runtime behavior is not validated through test execution. The verify-report will reflect static analysis findings rather than dynamic test results.