claude-product-management-skills

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.

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.

Analyzes why a shipped feature is or isn't being used, covering adoption metrics, barriers, user feedback signals, and recommended actions. Use after launching a feature to diagnose adoption issues.

Translates feature ideas into Jobs-to-Be-Done format with functional and emotional jobs, success criteria, and switching triggers. Use when reframing feature requests to understand the underlying user motivation.

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.

Shifts thinking from feature delivery to measurable user or business outcomes. Use before building a feature, during roadmap planning, or while defining success metrics to ensure work ties to real results.

Turns launches into structured learning by comparing expected vs actual outcomes and extracting key learnings. Use after any product launch to capture what worked, what didn't, and inform future decisions.

Evaluates PRD quality for clarity, testability, and build-readiness across problem clarity, scope, acceptance criteria, edge cases, and metrics. Use before sharing a PRD with engineering to catch gaps early.

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.

Identifies root causes behind declining user retention with likely causes, supporting evidence, and fix experiments. Use when you observe a retention drop and need to systematically diagnose why users are leaving.

Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.

Reveals hidden disagreements between stakeholders before execution begins. Use when kicking off cross-functional projects, planning launches, or sensing misalignment between teams on goals or priorities.

Clearly explains gains, losses, and reasoning behind a product decision. Use when communicating tradeoffs to stakeholders or documenting why a particular path was chosen over alternatives.

Identifies which user segment to focus on first using pain severity, willingness to pay, reachability, and strategic alignment. Use when choosing your initial target audience or re-evaluating segment focus.

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.