prd-validator

Validate PRD references, scope, and acceptance criteria against the codebase.

11|2|Updated Jan 19, 2026

Search Tags:#automation #codebase #requirements #validation #prd #acceptance-criteria #non-goals

Ready to run

npx skills add https://github.com/Viniciuscarvalho/Feature-marker --skill prd-validator-viniciuscarvalho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-validator
Source: https://github.com/Viniciuscarvalho/Feature-marker/tree/main/feature-marker-dist/feature-marker/resources/spec-workflow/skills/prd-validator
Command: npx skills add https://github.com/Viniciuscarvalho/Feature-marker --skill prd-validator-viniciuscarvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD validation is a bottleneck in early-stage product development. This skill automates cross-checks against the codebase, verifies scope realism, and classifies acceptance criteria for measurability, enabling teams to catch issues before TechSpec generation.

Core Features & Use Cases

Reference existence checks: Grep codebase for entities, services, endpoints, and UI components mentioned in a PRD.
Scope realism evaluation: Rates the number of requirements and flags scope creep indicators.
AC quality assessment: Classifies ACs as measurable or vague and proposes concrete quantifications.
Non-Goals validation: Ensures a Non-Goals section exists and suggests starter exclusions when missing.
PRD conflict detection: Scans for overlapping coverage with existing PRDs and surfaces conflicts.

Quick Start

Run the PRD validator on tasks/prd-<slug>/prd.md to generate .claude/feature-state/<slug>/prd-validation.md and resume from existing state if present.

Frequently Asked Questions about prd-validator

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

FAQPage Schema

How do I validate a PRD against my codebase to check for missing references?▼

To validate a PRD against your codebase, the tool scans tasks/prd-{slug}/prd.md to grep for mentioned entities and endpoints, generating a structured prd-validation.md file that surfaces missing references and suggested fixes.

What is PRD scope realism evaluation and how does it prevent scope creep?▼

PRD scope realism evaluation rates the number of requirements in your PRD and flags scope creep indicators, helping teams catch unrealistic scope boundaries before progressing to technical specification generation.

How do I check if my acceptance criteria are measurable or vague?▼

Acceptance criteria quality assessment classifies each AC as measurable or vague and proposes concrete quantifications, ensuring your PRD contains verifiable conditions rather than ambiguous statements before engineering begins.

Can I resume PRD validation from an existing state if the process was interrupted?▼

Yes, you can resume PRD validation from an existing state; the validator operates on tasks/prd-{slug}/prd.md and stores progress in .claude/feature-state/{slug}/prd-validation.md for continuity.

Does PRD validation detect conflicts with existing product requirement documents?▼

PRD conflict detection scans for overlapping coverage with existing PRDs and surfaces conflicts, ensuring new feature requirements do not contradict or duplicate previously defined product scope boundaries.

How do I ensure Non-Goals are defined in my PRD before technical spec generation?▼

Non-Goals validation ensures a Non-Goals section exists in your PRD and suggests starter exclusions when missing, securing product scope by explicitly documenting what the feature will not deliver.