prd-critic
Skill0 starsChanged 6 months agoMITView on GitHub
Red-team a PRD by simulating a skeptical PM, a senior engineer, and a target customer ripping it apart before you ship it for review. Use after drafting a PRD and before sharing with eng leads, exec reviewers, or other stakeholders. Triggers on phrases like "critique this PRD", "review my PRD", "find holes in this spec", "what's wrong with this PRD", "stress-test my spec", "PRD red team", "разнеси мой PRD", "найди дыры в спеке".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- yevhens-hue/claude-skills-starter-kittheir own version, first seen Aug 28, 2026
- pruthivim/claude-pm-skillstheir own version, first seen Jul 31, 2026
- pratikshadake/claude-product-management-skillstheir own version, first seen Feb 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- pratikshadake/claude-product-management-skills★ 33same name
- yevhens-hue/claude-skills-starter-kit★ 4same name
- pruthivim/claude-pm-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- ai-eval-scorerSkill
- deep-market-researchSkill
- feedback-triageSkill
- prd-builderSkill
- product-trio-sessionSkill
- synthetic-user-interviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use this before sharing the PRD with your real eng lead, designer, or exec sponsor.
- Distinctive: line 69
Always run these five checks against the PRD even if no reviewer raised them:
- Distinctive: line 77
If any check fails, add it to the punch list as Critical.
- Distinctive: line 111
All-Critical inflation: if everything is Critical, nothing is.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PRD Critic
Purpose
Most PRDs ship with the same five flaws: vague metrics, hidden assumptions, undefined scope, missing tradeoffs, and a solution that doesn't quite fit the problem. The author can't see them because they wrote them.
This skill puts the PRD through three hostile reviewers, each with a different angle, then consolidates a punch list of fixes.
Use this before sharing the PRD with your real eng lead, designer, or exec sponsor. It is cheaper to fix issues here than after political fallout.
When to use
- You just drafted a PRD and are about to circulate it
- A teammate sent you a PRD and you want a second-opinion review
- Your exec keeps sending PRDs back and you want to pre-empt the same comments
- You're about to put a PRD into product review or sprint planning
When NOT to use
- For documents that aren't PRDs (use
proofreador general review instead) - For PRDs at the discovery stage where structure is intentionally loose
- For ticket-level specs - the overhead isn't worth it
Inputs
Required:
- PRD content (paste, markdown file, or path)
Optional:
- Specific angle to emphasize ("the eng lead is concerned about scope", "exec is skeptical about ROI")
- Target reviewer audience (helps tune severity)
Process
Phase 1: Three reviewers
Set up three reviewer personas explicitly. They argue in their own voice:
The Skeptical PM (Director-level, 10+ years)
- Pokes at strategic fit, prioritization, opportunity cost
- Standard moves: "why this instead of X?", "what does this displace?", "what's the second-order effect?"
The Senior Engineer (Staff+ engineer who has shipped at scale)
- Pokes at scope, complexity, technical assumptions, hidden integration cost
- Standard moves: "this is two features stapled together", "you're hiding a migration here", "what happens when X fails?"
The Target Customer (the actual user, in their voice)
- Pokes at value, workflow fit, why they would actually switch
- Standard moves: "I already have a way to do this", "this solves the wrong half of the problem", "I'd never pay for this without X"
Each reviewer reads the PRD and lists their top 3-5 concerns in their voice.
Phase 2: Consolidation
Merge the three lists into a single ranked punch list:
- Severity (Critical / Major / Minor)
- Source (which reviewer raised it; if multiple, that's a signal)
- What the issue is (in plain language)
- Why it matters (the consequence if not fixed)
- What to do (concrete suggested edit)
Phase 3: The five killer checks
Always run these five checks against the PRD even if no reviewer raised them:
- Vague metrics: are success metrics directionally measurable with numbers?
- Empty Out-of-scope: does the PRD say what is explicitly NOT being built?
- Hidden assumptions: are key assumptions named or buried as fact?
- Missing tradeoffs: does the PRD claim pure upside?
- Solution-problem fit: would the solution actually solve the stated problem if shipped exactly as written?
If any check fails, add it to the punch list as Critical.
Phase 4: Suggested rewrite (optional)
For the top 3 Critical issues, draft replacement language the author can paste in. Not a full rewrite - surgical edits.
Output
# PRD Critique: [PRD title]
## TL;DR verdict (Ship / Revise / Rethink)
## Reviewer reactions
### Skeptical PM
### Senior Engineer
### Target Customer
## Killer checks (5/5)
## Punch list (ranked)
| # | Severity | Issue | Why it matters | Suggested fix |
## Suggested rewrites (top 3 Critical)
## What the PRD does well (do not cut these)The final "does well" section is mandatory. A critique that only finds flaws gets dismissed. Naming what's already strong builds trust and prevents over-rewriting.
Common failure modes to avoid
- Surface-only feedback: "improve clarity", "add metrics" - useless. Be specific or be quiet.
- Reviewer drift: each persona must stay in voice. The engineer doesn't care about brand consistency, the customer doesn't care about technical debt.
- All-Critical inflation: if everything is Critical, nothing is. Use the severity scale honestly.
- Skipping the "does well" section: this is where you signal you actually read the doc
Pair with
Best used in tandem with prd-builder. Build → critique → revise → share. The whole loop runs in under an hour.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

