← ClaudeAtlas

prd-review-challengerlisted

Critical review of PRDs, feature specs, and product decision documents — acts as a devil's advocate to surface weak assumptions, missing requirements, implementation risks, and logical gaps. Use when a PM or team lead wants to stress-test a document before team review, validate a spec before development starts, or identify what's missing in a product decision. Triggers RU: «проверь PRD», «разбери спецификацию», «найди дыры в PRD». Triggers EN: 'review my PRD', 'challenge my spec', 'find holes in my PRD', 'critique my feature spec'. Do not use for writing or rewriting PRDs.
KirKruglov/claude-skills-kit · ★ 9 · Code & Development · score 82
Install: claude install-skill KirKruglov/claude-skills-kit
# Skill: prd-review-challenger Acts as a devil's advocate for PRDs, feature specs, and product decisions. Surfaces weak spots, hidden assumptions, logical gaps, and overlooked risks — before the document goes to the team or into development. --- ## Triggers **Russian:** «проверь PRD», «разбери спецификацию», «найди дыры в PRD», «покритикуй спецификацию», «ревью PRD», «challenger для PRD», «что упущено в спецификации». **English:** "review my PRD", "challenge my spec", "find holes in my PRD", "critique my feature spec", "stress-test my PRD", "what's missing in my spec" --- ## Language Detection Detect the language of the input document — respond in that language. If a different language is explicitly requested, use it. --- ## Input **Required:** text of a PRD, feature spec, or product decision description (pasted directly into the conversation or provided as a file). **Optional:** context that sharpens the critique: - product target audience - project stage (0→1, scaling, redesign) - strategic constraints (timeline, tech stack, budget) - the angle that matters most right now (UX, technical complexity, business risks) ## Output A structured review report with five sections: 1. Weak spots and hidden assumptions 2. Open questions — what the PRD doesn't answer 3. Implementation and UX risks 4. Alternative approaches to consider 5. Completeness checklist with rating --- ## Instructions ### Step 1 — Accept the Document and Assess Its Type Receive the document text.