sdd-verify

Verifies SDCC implementation correctness against specs and design documents before committing.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/aroca89/roca_teams --skill sdd-verify-aroca89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-verify-aroca89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps orchestrated SDD changes from drifting away from specs, designs, and tasks by providing a verification gate that proves compliance before archiving.

Core Features & Use Cases

  • Structured evidence collection: Searches engram or openspec artifacts, retrieves proposals, specs, designs, and tasks, and checks task completion so you know nothing critical is missing.
  • Dynamic testing and validation: Detects the configured test and build commands, runs them, enforces coverage thresholds, and maps spec scenarios to real test results for behavioral compliance.
  • Persistent reporting and audit trails: Persists verification reports per the artifact store mode and summarizes compliance matrices, making it ideal for release reviews after implementer work.

Quick Start

Ask the orchestrator to run sdd-verify with the change name so it can compare specs, design, tasks, and tests before archiving.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I validate implementation correctness against specs and design documents?

Spec compliance validation compares your implementation against specs, designs, and tasks by collecting structured evidence. It runs configured build and test commands, enforces coverage thresholds, and maps spec scenarios to test results before archiving changes.

What is the best way to automate build validation and test execution in an SDD pipeline?

Automated build validation in an SDD pipeline detects configured test and build commands, executes them, and computes coverage. This dynamic testing enforces behavioral compliance by mapping spec scenarios directly to real test outcomes.

How does spec compliance verification handle artifact persistence and audit trails?

Spec compliance verification persists reports per the configured artifact store mode and summarizes compliance matrices. This creates persistent audit trails ideal for release reviews after implementer work is completed.

Can I enforce coverage thresholds and map spec scenarios to test results automatically?

Yes, you can enforce coverage thresholds automatically. The verification process detects test commands, runs them, computes coverage, and maps spec scenarios to real test results to prove behavioral compliance before archiving.

Why do orchestrated SDD changes drift away from specs, and how do I stop it?

Orchestrated SDD changes drift when there is no verification gate proving compliance before archiving. Applying a verification step retrieves proposals, specs, designs, and tasks, checking completion so nothing critical is missing.

What do I need to run sdd-verify within my change pipeline?

To run sdd-verify, ask the orchestrator to execute it with the change name. It requires engram or openspec artifacts containing proposals, specs, designs, and tasks to compare implementation correctness before archiving.