sdd-verify

Execute tests and validate TDD evidence for SDD implementations.

Updated May 9, 2026
One-click install
npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-verify-leandrobenjaminl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/LeandroBenjaminL/lend-ai/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-verify-leandrobenjaminl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, pytest-cov, coverage, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill serves as a quality gate for the Spec-Driven Development (SDD) cycle, ensuring that implementations are complete, correct, and meet specifications before they are archived.

Core Features & Use Cases

  • Implementation Verification: Checks for completeness, correctness, and spec compliance.
  • Test Execution: Runs tests to verify scenarios and detect regressions.
  • TDD Compliance: Validates Test-Driven Development evidence for strict adherence.
  • Quality Metrics: Analyzes code coverage and assertion quality.
  • Use Case: Before merging a code change, use this Skill to confirm that all critical tests pass and no regressions are present.

Quick Start

Run the sdd-verify skill to validate the current change before merging.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I verify test-driven development evidence and check for regressions before merging code?

To verify test-driven development evidence and check for regressions, you can execute tests, analyze code coverage, and validate TDD compliance to ensure quality gates are met before merging code changes.

What is the best way to check SDD implementation correctness and spec compliance?

Checking SDD implementation correctness involves executing tests and validating TDD evidence to confirm completeness, correctness, and spec compliance before archiving changes in the development cycle.

Can I use pytest to validate code coverage and assertion quality for spec-driven development?

Yes, you can use pytest and pytest-cov to validate code coverage and assertion quality, running tests to verify scenarios and detect regressions as part of the spec-driven development quality gate.

How do I ensure quality gates are met before archiving spec-driven development changes?

To ensure quality gates are met before archiving spec-driven development changes, execute tests to detect regressions, validate TDD compliance, and analyze code coverage metrics for implementation completeness.

Why does test execution fail to detect regressions in my SDD implementation?

Test execution may fail to detect regressions if TDD evidence is insufficient or assertion quality is low, requiring validation of test-driven development compliance and thorough code coverage analysis to ensure correctness.

Do I need pytest-cov and coverage to run spec-driven development verification?

Yes, you need pytest-cov and coverage dependencies to analyze code coverage metrics and validate assertion quality when running spec-driven development verification for implementation correctness.