sdd-verify

Validate code implementations against project specifications and design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately match design specifications, requirements, and defined tasks, acting as a critical quality gate before changes are finalized.

Core Features & Use Cases

  • Completeness Check: Verifies all tasks associated with a change are completed.
  • Correctness Validation: Compares implementation details against provided specifications and scenarios.
  • Design Coherence: Assesses whether the implementation adheres to the approved design decisions.
  • Test Coverage Analysis: Checks if adequate tests exist for the implemented features.
  • Use Case: After a developer completes a new feature, this Skill can be triggered to automatically review the code against the feature's requirements document, design mockups, and task list, flagging any discrepancies.

Quick Start

Use the sdd-verify skill to verify the completed change against the proposal and specs.

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?

Verifying code implementation against project specifications requires scanning the codebase for evidence of requirement fulfillment and scenario coverage to assess adherence to design decisions. This process acts as a quality gate to flag discrepancies before changes are finalized.

What is the best way to check if test coverage exists for implemented features?

Checking test coverage for implemented features involves scanning the codebase to validate that adequate tests exist for all completed tasks and scenarios. This ensures requirement fulfillment and adherence to the approved design decisions before finalizing changes.

Can I validate design coherence in a codebase after completing a new feature?

Yes, you can validate design coherence by triggering an automated review that compares the implementation details against provided specifications, design mockups, and the task list. It assesses whether the implementation adheres to approved design decisions and flags discrepancies.

How do I automate a completeness check for tasks associated with a code change?

Automating a completeness check involves scanning the codebase to verify all tasks associated with a change are completed, matching implementation details against requirements documents, and validating scenario coverage to flag any missing requirement fulfillment.

Does automated code review work without providing design documents and task lists?

Automated code review requires design documents, specifications, and task lists as input to accurately validate correctness and completeness. Without these references, the verification process cannot compare implementation details against approved design decisions or check for requirement fulfillment.