sdd-verify

Validates change implementation adherence to specs, design, and tasks, returning a structured verify-report.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-verify-maxculen86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/internal/assets/skills/sdd-verify
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-verify-maxculen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that a change implementation adheres to its specs, design, and tasks, acting as the quality gate in the orchestrator's verification phase.

Core Features & Use Cases

  • Static and dynamic verification of change artifacts (proposal, spec, design, tasks) against the spec.
  • Generates and persists a structured verify-report to the configured storage path, enabling audit trails and compliance checks.
  • Supports multiple persistence and reporting modes (engram, openspec, hybrid, none) as defined by the verification workflow.

Quick Start

Start a verification for a completed or partially completed change using the orchestrator's verify command.

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 change implementation adheres to its specs and design tasks?

Spec-driven verification validates completed or partially completed change artifacts by evaluating proposal, spec, design, and tasks against the original specification and generating a structured verify-report.

What is spec-driven verification for software engineering changes?

Spec-driven verification is a quality gate process that reads and enforces Section A–C requirements to ensure change implementations adhere to their specs, design, and tasks across engram, openspec, and hybrid modes.

How do I generate a structured verify-report for compliance checks?

You can generate a structured verify-report by running an orchestrator-driven verification phase, which persists the validation results for change artifacts to a configured storage path, enabling audit trails.

Does spec verification support engram, openspec, and hybrid persistence modes?

Yes, spec-driven verification supports multiple persistence and reporting modes, including engram, openspec, hybrid, and none, as defined by the orchestrator's verification workflow.

Can I validate partially completed change artifacts against the original spec?

Yes, you can start a verification process for either completed or partially completed changes using the orchestrator's verify command to evaluate artifacts against the specification.

Why does my change implementation fail the spec-driven quality gate?

A change implementation fails verification when it does not adhere to its specs, design, and tasks, meaning the submitted artifacts do not satisfy the Section A–C requirements enforced during the orchestrator-driven validation.