sdd-verify

Verify implementation compliance against specifications and design documents.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill sdd-verify-luisalbertomk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/LuisAlbertoMK/gentleman-agent-gh/tree/main/internal/assets/skills/sdd-verify
Command: npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill sdd-verify-luisalbertomk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of ensuring that implemented code changes strictly adhere to defined specifications, design documents, and task requirements, preventing quality drift in Spec-Driven Development.

Core Features & Use Cases

  • Automated Verification: Executes tests and performs source inspection to prove implementation matches specs and design.
  • Strict TDD Validation: Validates TDD cycle evidence and assertion quality to ensure tests are meaningful and robust.
  • Use Case: When a developer completes a feature, this skill acts as an independent quality gate, verifying that all requirements are covered by passing tests and that the implementation aligns with the architectural design.

Quick Start

Invoke the sdd-verify skill to perform a final verification of the current implementation against the project specifications and design artifacts.

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 compliance against specifications in a spec-driven development workflow?

Spec-driven development verification confirms implementation compliance by executing test suites, performing static source inspection, and validating TDD cycle evidence against design documents and task requirements.

What does automated TDD cycle validation check for in my test suite?

Automated TDD cycle validation checks assertion quality and behavioral compliance matrices to ensure tests are meaningful, robust, and properly cover all defined project phase requirements.

How do I set up an automated quality gate for spec-driven development artifacts?

Automated quality gating for spec-driven development operates by auditing assertions and executing tests to prove technical artifacts meet quality standards and align with architectural design before integration.

Can I use static source inspection to prevent quality drift in spec-driven development?

Static source inspection prevents quality drift in spec-driven development by independently validating that implemented code changes strictly adhere to defined specifications and design documents without relying solely on test execution.

When do I need to run behavioral compliance checks on my implementation?

Behavioral compliance checks are needed when a developer completes a feature, acting as an independent quality gate to verify that all requirements are covered by passing tests and architectural alignment.

What are the limitations of automated verification for spec-driven development?

Automated verification limitations include reliance on existing specifications and design documents, meaning it cannot validate unstated requirements or assess quality standards beyond defined TDD cycle evidence and test assertions.