mt-sdd-validate

Validate software implementations against SDD acceptance criteria and generate compliance reports.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill mt-sdd-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt-sdd-validate
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-sdd-validate
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-sdd-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of manually checking whether implemented changes conform to Software Design Document specifications and acceptance criteria.

Core Features & Use Cases

  • Specification Compliance Validation: Compares implementation changes against defined acceptance criteria and produces structured validation results.
  • Diff-Based Verification Workflow: Retrieves branch differences, delegates validation analysis, and aggregates findings including upstream change requests.
  • Use Case: When a development task has completed implementation, use this Skill to verify that every requirement in the specification is satisfied and identify any deviations requiring correction.

Quick Start

Use the mt-sdd-validate skill to validate the current implementation against the active SDD specification and generate a compliance report.

Frequently Asked Questions about mt-sdd-validate

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

FAQPage Schema
How do I validate code changes against software design document specifications?

To validate code changes against SDD specifications, compare implementation differences against defined acceptance criteria to produce structured conformity assessments and identify compliance gaps requiring correction.

What is specification compliance validation for implementation reviews?

Specification compliance validation is the process of comparing implemented changes against SDD acceptance criteria, analyzing git diffs, and generating structured validation reports to verify every requirement is satisfied.

How do I check if my git diff satisfies acceptance criteria from a specification document?

Checking if a git diff satisfies acceptance criteria requires retrieving branch differences, delegating validation analysis against the SDD, and aggregating findings including any upstream change requests into a compliance report.

What inputs do I need to generate a structured conformity assessment for SDD workflows?

Generating a structured conformity assessment requires session metadata, specification documents, and validation procedures to compare implementation changes and identify any deviations from defined acceptance criteria.

When should I use diff-based verification for specification compliance?

Use diff-based verification when a development task has completed implementation and you need to verify that every requirement in the SDD specification is satisfied and identify any deviations requiring correction.