Audit PRDs by comparing descriptions with current codebase entities and interfaces.
npx skills add https://github.com/rfhayn/forager --skill prd-audit-rfhayn
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
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.
context.save() calls to the actual implementation.To begin the PRD audit, execute the prd-audit skill and provide the path to the PRD you wish to verify.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
BrunoAMSilvaLocates official Microsoft API references and retrieves working code samples for SDK usage verification.
zcaceresAudits project documentation against the codebase and generates a structured revision plan.
bahayonghangSearch and validate code patterns using Tree-sitter structural queries.
canonicalCross-reference documentation claims, CLI commands, and API signatures against source code.