product-validate

Validate feature specs against a PRD baseline with read-only phase checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams ensure feature specs stay aligned with the Product Requirements Document (PRD) without making any changes to files, preventing scope creep and misalignment.

Core Features & Use Cases

  • Read-only validation: compares specs against PRD baseline for scope, personas, metrics, traceability, and boundary maps.
  • Traceability checks: maps each spec to PRD sections and identifies gaps.
  • Comprehensive reporting: generates a structured validation report with remediation recommendations, ready for product reviews.

Quick Start

Validate all specs against the PRD baseline to surface any alignment gaps.

Frequently Asked Questions about 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 baseline?

To validate feature specs against a PRD baseline, load the PRD and run phase checks for scope, personas, metrics, and traceability to generate a read-only alignment report.

What is PRD traceability and how does it detect scope creep?

PRD traceability maps each feature spec to specific PRD sections to identify alignment gaps, ensuring requirements stay within the original product scope and preventing scope creep.

How do I check if out-of-scope features exist in my product requirements?

You can check for out-of-scope features by applying boundary map validation across your specs, which detects requirements that fall outside the established PRD baseline without modifying files.

Can I validate a subset of feature specs instead of the entire PRD?

Yes, you can validate a given subset of feature specs by applying phase checks across only the provided specs, producing a structured validation report anchored to PRD references.

Does the PRD validation process modify my spec files?

No, PRD validation is a read-only process that compares feature specs against the baseline without modifying any files, outputting a structured report with remediation recommendations instead.