sdd-verify

Execute tests and build commands to verify changes against specs and tasks.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-verify-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-verify
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-verify-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that a finished or partially completed change satisfies the defined specs, design, and tasks by executing tests and collecting concrete evidence.

Core Features & Use Cases

  • End-to-end verification: loads the change, runs tests, builds, and validates compliance against specs.
  • Evidence-driven reporting: produces a verifiable verify-report that documents completeness and correctness.
  • Flexible persistence: supports engram, openspec, hybrid, or none artifact storage modes for audit trails.

Quick Start

Trigger this verification after a change is ready and review the produced report.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I automate end-to-end verification to prove my implementation matches specs?

Automated end-to-end verification executes your project's test and build commands, validating implementation compliance against defined specs, design, and tasks. It collects concrete evidence to prove changes align, persisting a verifiable report for audit trails.

What is evidence-driven compliance reporting in QA testing?

Evidence-driven compliance reporting runs tests and validates outputs against specifications to document completeness and correctness. It produces a verifiable verify-report proving that finished or partially completed changes satisfy defined project requirements.

Do I need specific artifact storage modes configured for evidence collection?

You can configure engram, openspec, hybrid, or none artifact storage modes for evidence collection. The configured artifact_store.mode determines how verification reports are persisted for audit trails and compliance tracking.

Does end-to-end verification work with hybrid workflow registries?

End-to-end verification applies across engram, openspec, and hybrid workflows. It reads project specifications and task data directly from the project registry or skill registry to validate changes.

What test commands and artifacts are required to run automated change verification?

Automated change verification requires access to the project's test commands, build commands, and specification artifacts. It enforces a strict evidence-driven evaluation by executing these commands and loading the change data from the registry.

When should I trigger end-to-end verification during the development lifecycle?

Trigger end-to-end verification after a change is ready or partially completed to validate compliance. It runs tests and builds to collect concrete evidence, ensuring the implementation matches specs before finalizing.