adlc-product-analyze

Detect gaps and drift between PDRs and PRDs across the repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze product documentation to ensure PDRs (Product Decision Records) and PRD (Product Requirements Document) are aligned, complete, and free of drift or quality gaps.

Core Features & Use Cases

  • Read-only validation of PDRs vs PRD to surface inconsistencies and gaps
  • Cross-PDR consistency checks and drift detection between system-level and feature-level artifacts
  • Structured reporting with remediation recommendations and actionable next steps
  • Staleness and placeholder detection to surface outdated references and missing content

Quick Start

Run the product analysis to review all artifacts and surface PDR/PRD inconsistencies.

Frequently Asked Questions about adlc-product-analyze

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

FAQPage Schema
How do I detect drift between a Product Decision Record and a PRD?

To detect drift between a Product Decision Record and a PRD, you can run a read-only validation across your repository to surface inconsistencies, gaps, and quality issues between system-level and feature-level artifacts.

What is PDR and PRD consistency analysis in product management?

PDR and PRD consistency analysis is a read-only validation process that identifies gaps between Product Decision Records and Product Requirements Documents, ensuring completeness and highlighting staleness or quality issues across the repository.

How do I check product documentation for staleness and missing placeholders?

You can check product documentation for staleness and missing placeholders by performing an automated analysis that detects outdated references and missing content, providing structured findings with remediation recommendations.

Does this product doc analysis require any special dependencies or setup?

This product doc analysis requires no special dependencies or setup, allowing you to directly run a read-only review across the entire repository to surface PDR and PRD inconsistencies without additional components.

Can I validate constitution alignment for feature-level PDRs against a system-level PRD?

You can validate constitution alignment for feature-level PDRs against a system-level PRD by running a cross-artifact consistency check that emphasizes read-only drift detection and provides structured findings with actionable next steps.