sdd-verify

Execute tests and validate software changes against project specifications.

10|Updated Feb 28, 2026

Search Tags:#automation #testing #verification #quality-assurance #code-review #specs

Ready to run

npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-verify-alan-thegentleman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/Alan-TheGentleman/gentle-ai-enterprise/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-verify-alan-thegentleman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a rigorous verification workflow to prove that a change is complete, correct, and behaviorally compliant with the project specifications by executing tests and collecting evidence.

Core Features & Use Cases

End-to-end verification: checks task completeness, correctness against specs, design coherence, test coverage, and build viability.
Evidence-driven reports: generates verifiable verification artifacts showing which requirements are satisfied or pending.
Change validation: supports orchestrated changes by consuming change-name, artifact-store mode, and dependencies to produce a detailed verification report.

Quick Start

Provide the orchestrator with a change name and artifact-store mode to run a full verification pass on the given 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 a code change is complete and compliant with project specs?▼

Spec verification proves a software change is complete and behaviorally compliant by running tests and validating the implementation against project specifications to generate an evidence-driven report.

What does end-to-end verification of a feature branch cover?▼

End-to-end verification covers task completeness, correctness against specs, design coherence, test coverage, build viability, and spec compliance to ensure the submitted change is fully validated.

How do I generate an evidence-driven verification report for a change?▼

Generate a verification report by providing the orchestrator with a change name and artifact-store mode, which executes a full verification pass and produces verifiable artifacts showing satisfied or pending requirements.

Can I validate test coverage and build viability for orchestrated code changes?▼

Yes, change validation supports orchestrated changes by consuming dependencies and artifact-store mode to execute tests, check coverage, validate builds, and produce a detailed verification report.

What is the best way to automate quality assurance reviews for feature branches?▼

Automated quality assurance verification applies to changes submitted to a codebase or feature branch, executing tests and validating against specs to prove the change is correct and behaviorally compliant.

Why does spec compliance verification require an artifact-store mode?▼

Artifact-store mode is required to consume orchestrated change dependencies, execute the verification workflow, and generate verifiable evidence artifacts showing which requirements are satisfied or pending.