mad-validate

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.