mh-cto-sdlc-prd-validate

Audit Product Requirement Documents for consistency, traceability, and epic mapping readiness.

2|Updated Apr 5, 2026

Search Tags:#audit #traceability #consistency check #product requirements #PRD validation

Ready to run

npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-prd-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mh-cto-sdlc-prd-validate
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/cto/sdlc/phase-2-product-definition/mh-cto-sdlc-prd-validate
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-prd-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill meticulously audits Product Requirement Documents (PRD) for internal consistency, traceability, and readiness for epic mapping, flagging invented features, uncovered goals, and constraint blindspots.

Core Features & Use Cases

PRD Validation: Audits the PRD for internal consistency, Phase 1 traceability, and readiness to begin epic mapping.
Feature & Goal Coverage: Ensures all Must-priority features have supporting Phase 1 artifacts and that every goal has a serving feature and metric.
Constraint and Assumption Analysis: Checks for hard constraints and active unverified assumptions, identifying any blindspots or invalidations.
Conditional Pass Requirements: Ensures all conditional pass requirements from Phase 1 are addressed in the PRD.
Validation Report Generation: Generates a detailed report highlighting findings, categorized as BLOCKING, REQUIRED, or ADVISORY.

Quick Start

Validate the PRD with the command: 'validate the PRD'

Frequently Asked Questions about mh-cto-sdlc-prd-validate

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

FAQPage Schema

How do I check my product requirements document for gaps before development?▼

To check your product requirements document for gaps, you can audit it for internal consistency and traceability. This process identifies uncovered goals, invented features, and constraint blindspots to ensure development readiness.

What is PRD validation and how does it ensure traceability?▼

PRD validation is the process of auditing a Product Requirement Document to ensure Phase 1 traceability and goal coverage. It verifies that every goal has a serving feature and metric, confirming the document is ready for epic mapping.

How do I validate that all features in a PRD have supporting artifacts?▼

You can validate feature coverage by auditing the PRD to ensure all Must-priority features have supporting Phase 1 artifacts. This check confirms that every feature is backed by necessary documentation and addresses conditional pass requirements.

Can I use a consistency check to find unverified assumptions in my PRD?▼

Yes, a consistency check can scan your PRD for hard constraints and active unverified assumptions. This identifies potential blindspots or invalidations that could disrupt the product development lifecycle.

How do I generate a validation report for a product requirements document?▼

You can generate a validation report by running an audit on your product requirements document. The report highlights findings categorized as BLOCKING, REQUIRED, or ADVISORY to indicate the severity of gaps and inconsistencies.

What are the limitations of automated PRD consistency checks?▼

Automated PRD consistency checks are limited to identifying structural gaps like missing metrics, uncovered goals, and invented features. They cannot assess the strategic viability or market accuracy of the documented requirements.