prd-critic
PRD Quality Critic
Purpose
Evaluate whether a PRD is clear, testable, and build-ready.
Evaluation Areas
- Problem clarity
- Scope definition
- Acceptance criteria
- Edge cases
- Metrics
- Ambiguity or missing detail
Output
Strengths
Gaps or Risks
Clarifying Questions
Rewrite Recommendations
More from pratikshadake/claude-product-management-skills
assumption-mapper
Exposes hidden risks by identifying and ranking assumptions across desirability, feasibility, and viability categories. Use when evaluating new products or features to surface the highest-risk assumption to test first.
23launch-readiness
Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.
22experiment-design
Designs fast, reliable validation experiments with hypothesis, method, success metric, and decision rules (Ship/Iterate/Kill). Use when you need to validate an assumption or test a product hypothesis before committing resources.
22value-vs-effort
Prioritizes features using structured scoring across user impact, revenue potential, strategic alignment, confidence, and engineering effort. Use when deciding which feature to build next or comparing competing priorities.
21roadmap-reality-checker
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
21problem-clarity
Evaluates whether a proposed idea addresses a genuine user problem worth solving. Use when assessing new feature ideas, startup concepts, or vague user complaints to determine if the pain justifies building a solution.
20