skills.rest
rinchsan
rinchsanCOMMUNITY
Explore all skills by this author →
𝕏@rinchsanGitHub

prd-review

Reviews PRD and spec documents on a Git branch and produces a structured quality verdict.

5|Updated Jul 8, 2019
Search Tags:#pull request#github#requirements#product management#spec review#git diff#prd review
One-click install
npx skills add https://github.com/rinchsan/dotfiles --skill prd-review-rinchsan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-review
Source: https://github.com/rinchsan/dotfiles/tree/main/.claude/skills/prd-review
Command: npx skills add https://github.com/rinchsan/dotfiles --skill prd-review-rinchsan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, teams need confidence that PRD and spec documents are complete and well-formed. This Skill automates that gate by diffing a branch against its base, locating PRD files, gathering PR and linked-issue context, and delegating a structured quality review. ## Core Features & Use Cases - Automatic PRD Detection: Diffs a branch against its base and identifies PRD/spec candidates by filename and path patterns, including Japanese terms like 要件 and 仕様. - Rich Context Gathering: Pulls PR titles, descriptions, comments, and linked GitHub issues (same-repo, cross-repo, or full URL) to inform the review. - Structured Verdict: Delegates to a prd-reviewer agent that produces a severity-ranked report (CRITICAL to LOW) with a summary table and final verdict. - Use Case: A product manager pushes a branch containing a new spec document and asks for a review before handing it to engineering; the Skill fetches the branch, reads the spec, checks linked issues for business context, and returns a completeness verdict. ## Quick Start Ask the assistant to review the PRD on your current feature branch against main before implementation begins.

Frequently Asked Questions about prd-review

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

FAQPage Schema
How do I review a PRD on a Git branch before implementation?▼

Provide the branch name and optionally a base branch (defaulting to main). The Skill fetches remote refs, diffs the branch, locates PRD files, and delegates a structured review that ends with a severity-ranked report and verdict.

How does the skill find PRD or spec files in a branch?▼

It runs git diff between the base and branch, then filters changed files for document extensions (.md, .txt, .rst) whose path or filename contains prd, spec, requirement, 要件, or 仕様. All matching candidates are reviewed.

Does the PRD review use linked GitHub issues as context?▼

Yes. It scans the PR description for issue references in short form (#123), cross-repo form (org/repo#123), or full URLs, then fetches each issue's title, body, and comments with the GitHub CLI to inform the completeness assessment.

What happens if no PRD files are found on the branch?▼

The Skill reports that no PRD files were detected and stops. It also stops early if the remote branch does not exist, verifying it first with git ls-remote.

Can I review a PRD without checking out the branch locally?▼

Yes. The Skill reads file contents directly from the remote ref using git show origin/branch:path, so no local checkout is required. It only needs git fetch to update remote refs first.

Related Skills

Explore More Product & Management Skills→
tomholfordtomholford
6

write-a-prd

Create a PRD from interviews, codebase exploration, and module design.

Community
Advanced
TencentBlueKingTencentBlueKing
839

bk-monitor-tapd-dev

Analyze TAPD tickets and generate a structured development plan.

Official
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
hicucuhicucu

sync-docs-from-diff

Generate non-destructive documentation update proposals from Git diffs.

Community
Advanced