prd-validate

Lints PRD files for missing sections, metadata, placeholders, formatting, and table integrity.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-validate
Source: https://github.com/sinositato/tato-claude-plugins/tree/main/plugins/prd-builder/skills/prd-validate
Command: npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill quickly checks your Product Requirements Document (PRD) for common structural and formatting errors, ensuring consistency before deeper analysis.

Core Features & Use Cases

  • Linting: Catches missing sections, incomplete metadata, placeholder text, and incorrect formatting.
  • Speed: Significantly faster than a full /prd-analyze, ideal for quick checks.
  • Use Case: After drafting a new feature PRD, run this skill to immediately identify any critical structural issues before sharing it for review.

Quick Start

Validate the structure of the PRD file located at 'prd/my-feature/prd.md'.

Frequently Asked Questions about prd-validate

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

FAQPage Schema
How do I check a PRD for missing sections and formatting errors?

To check a PRD for missing sections and formatting errors, run a lightweight linting tool that performs a structural consistency check, verifying section presence, metadata completeness, and table integrity to identify issues in a read-only report.

What is a PRD structural validation and when do I need it?

PRD structural validation is a read-only linting process that checks requirement formatting and placeholder markers in your document. You need it after drafting a new feature PRD to identify critical structural issues before sharing it for review.

How do I validate requirement formatting and metadata completeness in a PRD file?

You can validate requirement formatting and metadata completeness by running an automated lint check on your PRD file. The process scans the document and outputs a terminal report identifying specific structural and formatting issues without modifying the original file.

What is the best way to quickly check for placeholder markers in documentation?

The best way to quickly check for placeholder markers in documentation is to use a fast linting process. This approach catches incomplete metadata and placeholder text significantly faster than a full analysis, providing a terminal report of specific issues.

Does PRD linting modify my original document files?

PRD linting operates as a read-only terminal report and does not modify your original document files. It only scans the file to identify specific structural issues like table integrity problems and incorrect formatting without altering the source content.