review-prd

Review Ralph PRD user stories against code, tests, and browser behavior.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing Ralph PRD user stories manually is time-consuming and error-prone because each acceptance criterion may require code inspection, tests, and browser verification across branches and varying project setups. This Skill consolidates repository context, test results, and UI checks to produce clear, actionable verification outcomes for each story.

Core Features & Use Cases

  • Repo-wide checks: Run typechecks, linters, and the full test suite once to establish baseline results used by multiple stories.
  • Per-story verification: Inspect code changes, run story-specific tests, and perform browser-driven verification for UI and behavior criteria.
  • Structured reporting: Produce a PASS / GAP / UNTESTABLE summary with file paths, line references, and reproduction notes for QA, reviewers, or automated workflows.
  • Use Case: A reviewer validating a feature branch produced by Ralph can run this Skill to confirm each user story's acceptance criteria before merging.

Quick Start

Use the review-prd skill to review the project's prd.json on the target branch and produce a PASS/GAP/UNTESTABLE summary of each user story.

Frequently Asked Questions about review-prd

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

FAQPage Schema
How do I verify PRD user stories against code and tests?

PRD acceptance criteria verification requires running repo-wide typechecks, linters, and test suites, then inspecting code changes and performing browser verification to produce PASS, GAP, or UNTESTABLE summaries for each user story.

What does a PRD user story review report include?

A PRD user story review report includes a PASS, GAP, or UNTESTABLE status for each user story, supported by file paths, line references, and reproduction notes for QA and reviewers.

Do I need a dev server to validate PRD acceptance criteria?

Yes, validating PRD acceptance criteria requires starting a dev server for browser verification. You also need repository access, prd.json, CLAUDE.md testing instructions, and the ability to run typecheck and lint commands.

How do I review Ralph PRD user stories before merging a feature branch?

Review Ralph PRD user stories before merging by running repo-wide checks for a baseline, then inspecting code changes, running story-specific tests, and performing browser-driven UI checks to confirm acceptance criteria.

When should I mark a PRD user story as UNTESTABLE during code review?

Mark a PRD user story as UNTESTABLE during code review when acceptance criteria cannot be confirmed through code inspection, test results, or browser behavior due to missing dependencies or inaccessible UI states.