sdd-verify

Validate software implementation against specifications, design documents, and task completion.

Updated Feb 21, 2026

Search Tags:#testing #quality assurance #code review #verification #compliance #sdd

Ready to run

npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill sdd-verify-josemartinrodriguezmortaloni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/josemartinrodriguezmortaloni/opencode-config/tree/main/skill/sdd-verify
Command: npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill sdd-verify-josemartinrodriguezmortaloni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a crucial quality gate, ensuring that software implementations precisely align with the defined specifications, design documents, and planned tasks, preventing deviations and ensuring adherence to requirements.

Core Features & Use Cases

Completeness Check: Verifies all planned tasks are completed.
Correctness Validation: Compares code implementation against detailed specifications and scenarios.
Design Coherence: Assesses if the implementation adheres to architectural design decisions.
Testing Verification: Checks for adequate test coverage for implemented features.
Use Case: After a developer completes a new feature, this Skill is triggered to automatically review the code against the original requirements and design documents, flagging any discrepancies before the change is merged.

Quick Start

Use the sdd-verify skill to verify the implementation of the 'user-authentication' change.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema

How do I verify my code implementation matches software specifications?▼

To verify code implementation matches software specifications, you need a quality assurance gate that systematically checks completeness, correctness, and design coherence against your specification and design documents. This prevents deviations and ensures adherence to requirements.

What's the best way to check if all planned development tasks are completed?▼

Checking if all planned development tasks are completed involves validating the project's task completion status against the original specifications. This completeness check ensures every planned item is finished and correctly implemented before merging changes.

How do I validate test coverage for newly implemented features?▼

Validating test coverage for newly implemented features requires testing verification that checks for adequate coverage against your detailed specifications and scenarios. This ensures all implemented functionality is properly tested before changes are merged.

Can I assess if my code adheres to architectural design decisions automatically?▼

Yes, you can assess if your code adheres to architectural design decisions automatically by performing a design coherence check. This compares your software implementation directly against the defined design documents to flag any architectural discrepancies.

Do I need specification and design documents to validate software implementation?▼

Yes, you need specification and design documents to validate software implementation. Comprehensive analysis requires access to proposal, specs, design, tasks, and project configuration files to accurately compare the code against defined requirements.

When do I need to run a verification check in a Spec-Driven Development workflow?▼

You need to run a verification check in a Spec-Driven Development workflow after a developer completes a new feature. This automatically reviews the code against original requirements and design documents, flagging discrepancies before the change is merged.