prioritize-assumptions
This Claude Code skill evaluates a list of assumptions using an Impact × Risk matrix to determine testing priorities and suggest targeted experiments. Use it when triaging assumptions for a product or strategy, deciding which assumptions to validate first, or applying assumption prioritization methodologies like ICE or RICE scoring frameworks to guide resource allocation and experiment design.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/prioritize-assumptions && cp -r /tmp/prioritize-assumptions/pm-product-discovery/skills/prioritize-assumptions ~/.claude/skills/prioritize-assumptionsSKILL.md
## Prioritize Assumptions Triage assumptions using an Impact × Risk matrix and suggest targeted experiments. ### Context You are helping prioritize assumptions for **$ARGUMENTS**. If the user provides files with assumptions or research data, read them first. ### Domain Context **ICE** works well for assumption prioritization: Impact (Opportunity Score × # Customers) × Confidence (1–10) × Ease (1–10). Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1 (Dan Olsen). **RICE** splits Impact into Reach × Impact separately: (R × I × C) / E. See the `prioritization-frameworks` skill for full formulas and templates. ### Instructions The user will provide a list of assumptions to prioritize. Apply the following framework: 1. **For each assumption**, evaluate two dimensions: - **Impact**: The value created by validating this assumption AND the number of customers affected (in ICE: Impact = Opportunity Score × # Customers) - **Risk**: Defined as (1 - Confidence) × Effort 2. **Categorize each assumption** using the Impact × Risk matrix: - **Low Impact, Low Risk** → Defer testing until higher-priority assumptions are addressed - **High Impact, Low Risk** → Proceed to implementation (low risk, high reward) - **Low Impact, High Risk** → Reject the idea (not worth the investment) - **High Impact, High Risk** → Design an experiment to test it 3. **For each assumption requiring testing**, suggest an experiment that: - Maximizes validated learning with minimal effort - Measures actual behavior, not opinions - Has a clear success metric and threshold 4. **Present results** as a prioritized matrix or table. Think step by step. Save as markdown if the output is substantial. --- ### Further Reading - [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.