prd-review

Fact-check PRD claims against repository code and architecture.

2|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/andrewthetechie/andrew-skills --skill prd-review-andrewthetechie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-review
Source: https://github.com/andrewthetechie/andrew-skills/tree/main/prd-review
Command: npx skills add https://github.com/andrewthetechie/andrew-skills --skill prd-review-andrewthetechie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch incorrect assumptions, outdated requirements, and architecture mismatches in a PRD before implementation begins.

Core Features & Use Cases

  • Fact-checking against the codebase: Verifies claims about modules, APIs, data models, tests, and repo conventions using source files and documentation.
  • Architecture critique: Evaluates whether a proposed design fits existing boundaries, ADRs, and local patterns.
  • Review-ready reporting: Produces a claim matrix, severity-ranked findings, verified anchors, and open questions for decision-making.
  • Use case: A product or engineering lead can use it to sanity-check a technical proposal against the actual repository before work is started.

Quick Start

Ask the skill to review a PRD or technical proposal against the repository and report any unsupported or contradictory claims.

Frequently Asked Questions about prd-review

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

FAQPage Schema
How do I validate a technical proposal against an existing codebase?

To validate a technical proposal against an existing codebase, you can review the PRD by fact-checking claims and evaluating the proposed architecture against existing code, domain context, and ADRs.

What is a PRD review for repository-backed products?

A PRD review for repository-backed products is a pre-build validation process that catches incorrect assumptions, outdated requirements, and architecture mismatches by verifying technical claims against actual source files and documentation.

Can I check if a proposed design fits existing ADRs and local patterns?

Yes, architecture critique evaluates whether a proposed design fits existing boundaries, ADRs, and local patterns, ensuring the technical proposal aligns with established repository conventions before implementation begins.

How do I fact-check claims about modules and APIs in a product requirements document?

Fact-checking claims about modules and APIs involves verifying statements in the PRD against actual repository source files and documentation to identify unsupported or contradictory claims.

What is the best way to generate a claim matrix for design reviews?

Generating a claim matrix for design reviews requires evidence-based claim verification, producing severity-ranked findings, verified anchors, and open questions to support decision-making.

When do I need pre-build validation for a technical proposal?

Pre-build validation is needed before implementation begins to sanity-check a technical proposal, ensuring that assumptions, requirements, and architecture mismatches are caught early against the actual repository.