sdd-verify

Validate implementation alignment with specs, design, and tasks via builds and tests.

1|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-verify-ramonsdka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-verify-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that implementations align with specs, design, and tasks, serving as a rigorous quality gate for SDD-driven changes.

Core Features & Use Cases

  • End-to-end verification across proposal, spec, design, and tasks to ensure compliance with requirements.
  • Dynamic artifact handling across Engram, OpenSpec, Hybrid, or None modes, with evidence persistence.
  • Executes real tests and collects observational data to build a verifiable report of compliance.

Quick Start

Load the sdd-verify skill and trigger it to validate a completed or partial change against specs, design, and tasks, producing a formal verification report.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I verify that code changes align with specifications and design tasks?

To verify code changes align with specifications, you need a validation process that checks implementations against project artifacts like proposals, specs, and design tasks, producing a formal compliance report.

What is spec-driven development verification and when is it needed?

Spec-driven development verification is a quality assurance process that validates implementations against documented specs and design tasks. It is needed when you require a rigorous compliance gate for SDD-driven architectural changes.

Does the verification process support different artifact storage modes like Engram or OpenSpec?

Yes, the verification process supports multiple artifact store modes including Engram, OpenSpec, Hybrid, and None, dynamically retrieving project artifacts to validate changes across different storage conventions.

How do I execute tests and collect observational data for a quality assurance report?

You execute tests and collect observational data by running real builds and retrieving full observations, which are then compiled into a verifiable compliance report adhering to your configured storage conventions.

What are the limitations of using automated code review for architectural compliance?

Automated code review for architectural compliance requires accessible project artifacts like specs and tasks. Without proper artifact storage modes configured, the verification process cannot retrieve the necessary design documents to validate implementations.

Can I generate a verification report for partial changes without a completed implementation?

Yes, you can generate a verification report for partial changes. The validation process operates across proposal, spec, design, and task artifacts to assess compliance even when the implementation is not fully complete.