mad-validate

Automate end-to-end validation of feature specifications against implementation.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mad-validate
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/mad-validate
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually validating feature specifications against implementation is time-consuming and error-prone, leading to missed contract mismatches, vague requirements, untested user stories, and drifting documentation that causes rework and delayed releases.

Core Features & Use Cases

  • 4 Independent Validation Lenses: Check contract traceability, spec linting, test coverage, and living documentation sync sequentially or in parallel via Agent Teams.
  • Extended Validation Checks: Run E2E test coverage validation, pattern compliance audits, verification spec validation, and staleness detection to ensure implementation matches baseline expectations.
  • Use Case: A feature team building a new payment processing flow can use this skill to automatically verify API contracts match the implemented routes, catch vague requirement language, ensure all P1 user stories have test coverage, and flag any implementation details leaked into the spec.

Quick Start

Use the mad-validate skill to run the full automated validation suite on your active feature work item and receive a prioritized list of spec, implementation, and test issues to resolve.

Frequently Asked Questions about mad-validate

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

FAQPage Schema
How do I automate feature specification validation against code implementation?

Feature specification validation is automated by running end-to-end checks that compare implemented code against spec contracts to catch mismatches, requirement gaps, and documentation drift before deployment.

What is contract traceability and how does it catch API mismatches before deployment?

Contract traceability verifies that implemented API routes match defined specifications, catching contract mismatches automatically during feature delivery to prevent integration failures and rework.

How do I check test coverage for all P1 user stories in a feature workflow?

Test coverage analysis validates that all P1 user stories have corresponding tests by auditing E2E coverage, spec linting, and pattern compliance across the active feature work item.

Can I run spec linting and documentation sync checks in parallel for full-stack projects?

Spec linting and documentation sync checks can run in parallel via Agent Teams, applying four independent validation lenses to full-stack and desktop application project types simultaneously.

What's the best way to detect documentation drift and stale specs in software development?

Documentation drift and stale specs are detected through living documentation sync checks and staleness detection, ensuring implementation details match baseline expectations and flagging leaked spec content.

How do I enforce quality gates and traceability thresholds for MAD governance?

Quality gates and traceability thresholds are enforced by applying artifact contracts across feature delivery workflows, satisfying MAD governance discipline requirements for both sequential and parallel agent team execution.