pm-advisor-torres

Analyzes product discovery problems using Teresa Torres's continuous discovery frameworks and opportunity solution trees.

187|12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-advisor-torres-luyu2026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-advisor-torres
Source: https://github.com/Luyu2026/Skill-Bible/tree/main/pm-advisory-suite/pm-advisor-torres
Command: npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-advisor-torres-luyu2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often jump straight to building features without validating whether they connect to real user opportunities or measurable outcomes. This Skill applies Teresa Torres's Continuous Discovery method to structure user discovery, decompose outcomes into opportunity trees, and test the riskiest assumptions before committing to solutions. ## Core Features & Use Cases - Opportunity Solution Tree structuring: Maps outcomes to user opportunities, solutions, and assumption tests so every feature traces back to evidence. - Assumption testing guidance: Identifies the riskiest assumption behind a proposed solution and designs the smallest experiment to validate it. - Continuous discovery cadence coaching: Helps teams establish weekly lightweight user touchpoints instead of one-off heavy research phases. - Use Case: A PM asks whether to build a requested feature. The Skill reframes it as an opportunity, checks which outcome it serves, and proposes a minimal assumption test to run this week. ## Quick Start Ask the assistant to analyze your product discovery question using the Teresa Torres perspective, pasting your current situation, user research notes, or proposed solution.

Frequently Asked Questions about pm-advisor-torres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an opportunity solution tree for my product?▼

Start by defining a measurable outcome, then attach user opportunities gathered from interviews, then map candidate solutions under each opportunity, and finally list assumption tests at the bottom. Every solution must trace back to an opportunity and every opportunity to the outcome.

What is continuous discovery in product management?▼

Continuous discovery is the habit of the product trio (PM, designer, engineer) touching customers at least weekly and using those touchpoints to make decisions. It replaces one-off heavy research phases with frequent lightweight conversations.

How do I test assumptions before building an MVP?▼

Identify the riskiest assumption behind your solution across desirability, usability, feasibility, viability, and ethics, then design the smallest experiment that could falsify it. Only invest in building after that assumption survives testing.

Does continuous discovery work for B2B products with few users?▼

The weekly touchpoint cadence is hard to apply directly in B2B with long sales cycles, compliance limits, or scarce users. The method needs adaptation such as lower frequency and mixing in proxy data like sales feedback and support tickets.

What is the difference between outcome and output in product discovery?▼

An outcome is a measurable change in user behavior or business results, while an output is a delivered feature. Discovery should start from a clear outcome, since an opportunity tree without one has no root to trace decisions back to.