Agent skill · product strategy · alirezarezvani
product-discovery
Validate product ideas: map assumptions, plan discovery sprints, test problem-solution fit. Use whenever the user asks if an idea is worth building.
Why this skill is useful
Adds a CLI utility for assumption mapping that provides prioritized test plans based on risk and certainty, which the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 2k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Product Discovery Run structured discovery to identify high-value opportunities and de-risk product bets. When To Use Use this skill for: Opportunity Solution Tree facilitation Assumption mapping and test planning Problem validation interviews and evidence synthesis Solution validation with prototypes/experiments Discovery sprint planning and outputs Core Discovery Workflow 1. Define desired outcome Set one measurable outcome to improve. Establish baseline and target horizon. 2. Build Opportunity Solution Tree (OST) Outcome -> opportunities -> solution ideas -> experiments Keep opportunities grounded in user evidence, not internal opinions. 3. Map assumptions Identify desirability, viability, feasibility, and usability assumptions. Score assumptions by risk and certainty. Use: 4. Validate the problem Conduct interviews and behavior analysis. Confirm frequency, severity, and willingness to solve. Reject weak opportunities early. 5. Validate the solution Prototype before building. Run concept, usability, and value tests. Measure behavior, not only stated preference. 6. Plan discovery sprint 1-2 week cycle with explicit hypotheses Daily evidence reviews End with decision: proceed, pivot, or stop Opportunity Solution Tree (Teresa Torres) Structure: Outcome: metric you want to move Opportunities: unmet customer needs/pains Solutions: candidate interventions Experiments: fastest learning actions Quality checks: At least 3 distinct opportunities before converging. At least 2 experiments per top opportunity. Tie every branch to evidence source. Assumption Mapping Assumption categories: Desirability: users want this Viability: business value exists Feasibility: team can build/operate it Usability: users can successfully use it Prioritization rule: High risk + low certainty assumptions are tested first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/product-discovery--60d8fe