adlc-product-validate

Validate SPEC.md files against PRD requirements and generate structured reports.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-product-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adlc-product-validate
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-product-validate
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-product-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a strictly read-only validation of feature specifications to ensure they align with the Product Requirements Document (PRD), preventing drift between product intent and technical specs.

Core Features & Use Cases

  • Validate PRD scope alignment across specs and detect out-of-scope work.
  • Confirm persona alignment and metric consistency with the PRD.
  • Generate a structured validation report without modifying any source files for easy review and traceability.

Quick Start

Submit a SPEC.md or a directory of specs to run a read-only validation and receive a comprehensive report.

Frequently Asked Questions about adlc-product-validate

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

FAQPage Schema
How do I validate feature specs against a PRD to detect scope drift?▼

You can validate feature specs against a PRD by submitting a single SPEC.md file or a specs directory to generate a structured read-only validation report. The workflow checks PRD scope alignment, persona consistency, and metric traceability.

Can I validate an entire directory of SPEC.md files at once?▼

Yes, the validation workflow accepts a single SPEC.md, an entire specs directory, or all specs under a target path. It processes varied validation targets to produce a comprehensive structured report covering all submitted files.

Does spec validation modify my original source files during the review?▼

No, the validation workflow enforces strictly read-only constraints and generates a structured report without modifying any source files. Your original SPEC.md files remain completely untouched during the PRD alignment review process.

What does PRD traceability validation check for in feature specifications?▼

PRD traceability validation checks for mandated PRD references, scope alignment, persona consistency, and metric alignment within feature specs. It identifies out-of-scope work and reports any misalignment between product intent and technical specifications.

What is the best way to ensure feature specs align with product requirements without altering them?▼

The best way to ensure alignment is a read-only validation workflow that enforces PRD traceability and reports misalignment in a structured format. It confirms persona alignment and metric consistency while preventing drift between product intent and specs.