sdd-verify

Validate code implementations against specifications, design documents, and task lists.

1|1|Updated Jul 31, 2025

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

Ready to run

npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-verify-joaquinfontaana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/JoaquinFontaana/alquileres/tree/main/.agents/skills/sdd-verify
Command: npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-verify-joaquinfontaana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a quality gate, ensuring that code implementations accurately match predefined specifications, design documents, and task requirements, thereby preventing the integration of faulty or incomplete changes.

Core Features & Use Cases

Completeness Check: Verifies that all defined tasks are completed.
Correctness Validation: Compares code against detailed specifications and scenarios.
Coherence Assurance: Ensures adherence to design decisions and file structure.
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 feature's requirements and design, flagging any discrepancies before the change is merged.

Quick Start

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

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 implementation against project specifications before merging?▼

To verify code implementation against project specifications, you can use an automated quality gate that analyzes proposal documents, delta specifications, and task lists to generate a comprehensive verification report flagging discrepancies before integration.

What is the best way to check task completion status and test coverage for a new feature?▼

Checking task completion status and test coverage requires validating the implemented code against predefined design documents and task requirements, ensuring that all defined tasks are completed and adequate testing coverage exists for the new features.

How does validating code against design documents and requirements work?▼

Validating code against design documents works by systematically analyzing provided artifacts such as proposal documents and design outlines to check for completeness, correctness against requirements, coherence assurance, and adherence to design principles.

Can I use automated verification to ensure adherence to design decisions and file structure?▼

Yes, you can use automated verification to ensure adherence to design decisions and file structure by comparing the actual code implementation against detailed specifications, design outlines, and delta specifications to assure overall project coherence.

Does specification verification require specific proposal documents or design outlines?▼

Specification verification requires specific input artifacts such as proposal documents, delta specifications, design outlines, and task lists to systematically compare the code implementation against requirements and generate an accurate verification report.

Why does code verification flag discrepancies between implementation and requirements?▼

Code verification flags discrepancies between implementation and requirements to prevent the integration of faulty or incomplete changes, acting as a quality gate that ensures code implementations accurately match predefined specifications and task requirements.