prd-audit

Audit PRDs by comparing descriptions with current codebase entities and interfaces.

2|Updated Aug 15, 2025

Search Tags:#codebase verification #code accuracy #PRD audit #api signature verification #core data model

Ready to run

npx skills add https://github.com/rfhayn/forager --skill prd-audit-rfhayn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-audit
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/prd-audit
Command: npx skills add https://github.com/rfhayn/forager --skill prd-audit-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures code accuracy by auditing Product Requirement Documents (PRD) against the current codebase before implementation, verifying that entity names, property names, and API signatures match the current state.

Core Features & Use Cases

Entity Verification: Checks entity names and properties in PRDs against Core Data Models.
API and Interface Verification: Compares function, method, or API references in PRDs to actual code signatures.
File and Structure Verification: Validates referenced files and directories against current code structure.
Save Count Verification: Counts and compares PRD-reported context.save() calls to the actual implementation.

Quick Start

To begin the PRD audit, execute the prd-audit skill and provide the path to the PRD you wish to verify.

Frequently Asked Questions about prd-audit

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

FAQPage Schema

How do I audit a PRD against my current codebase?▼

To audit a PRD against your current codebase, execute the prd-audit script and provide the file path. The tool verifies that entity names, properties, and API signatures match your existing code structure.

What does codebase verification for PRDs check for?▼

Codebase verification for PRDs checks that entity names, property names, file structures, and API signatures in the document match the current code. It also counts and compares reported context.save() calls to actual implementations.

When do I need to verify API signatures in a PRD?▼

You need to verify API signatures in a PRD when the document is over two weeks old. This ensures that function, method, and API references remain accurate against the current codebase before you begin implementation.

Can I validate core data models referenced in a PRD automatically?▼

Yes, you can validate core data models referenced in a PRD automatically by running the script with the document path. It compares the referenced entity names and properties directly against the current codebase.

Does the PRD audit require access to specific file paths?▼

Yes, PRD audit requires access to your codebase paths to compare document descriptions with current entities and interfaces. You must provide the path to the PRD you wish to verify for the script to execute successfully.