PM Frameworks Encoded in the Opportunity Solution Tree Skill: A Deep Dive into the phuryn/pm-skills Repository

The Opportunity Solution Tree skill embeds five distinct product management frameworks—Teresa Torres's OST and Continuous Discovery Habits, Dan Olsen's Opportunity Score, the Product Trio model, and Alberto Savoia's skin-in-the-game experiments—to structure continuous product discovery workflows.

The phuryn/pm-skills repository provides structured AI skills for product management workflows. Within the opportunity-solution-tree skill, multiple battle-tested PM frameworks are encoded to guide teams through outcome-based discovery and opportunity prioritization.

The Five PM Frameworks Embedded in the Skill

Teresa Torres's Opportunity Solution Tree (OST)

In pm-product-discovery/skills/opportunity-solution-tree/SKILL.md (lines 12-15), the skill implements Torres's visual framework that maps desired outcomes → opportunities → solutions → experiments. This structure serves as the primary backbone for organizing product discovery efforts, described specifically as "a visual framework for structuring continuous product discovery" linked to Torres's Continuous Discovery Habits.

Continuous Discovery Habits Methodology

Line 12 of the same file references Torres's broader methodology as the "backbone of modern product discovery." This establishes the weekly cadence of customer interviews and opportunity mapping that defines the OST approach, ensuring teams engage in continuous rather than sporadic discovery.

Dan Olsen's Opportunity Score (The Lean Product Playbook)

At lines 18-19, the skill incorporates Olsen's prioritization metric from The Lean Product Playbook: Importance × (1 − Satisfaction). This Opportunity Score enables teams to rank customer opportunities objectively before committing resources to solution generation, explicitly citing Dan Olsen as the source.

The Product Trio Collaboration Model

Line 20 specifies that the Product Trio—comprising the Product Manager, Designer, and Engineer—should generate multiple solutions per opportunity. This embeds contemporary cross-functional collaboration practices directly into the skill's workflow, ensuring diverse perspectives during solution ideation.

Alberto Savoia's Skin-in-the-Game Experiments

Rather than relying on opinion-based validation, line 22 mandates "skin-in-the-game" experiments, reflecting Savoia's principle that true validation requires real commitment and measurable stakes. This approach distinguishes the skill from traditional research methods by requiring concrete evidence through experimental commitment.

Practical Implementation: Invoking the Skill

To activate these frameworks in a Claude-powered workflow, structure your prompt as follows:

{
  "skill": "opportunity-solution-tree",
  "arguments": {
    "outcome": "Increase 7‑day retention to 40%",
    "research": "Interview notes, NPS survey, analytics dashboards"
  }
}

This invocation triggers a four-step process grounded in the embedded frameworks:

1. Define the desired outcome using Torres's OST structure.
2. Surface 3-7 customer opportunities prioritized by Olsen's Opportunity Score.
3. Generate ≥3 solutions per opportunity via the Product Trio collaboration model.
4. Propose skin-in-the-game experiments for validation following Savoia's methodology.

Summary

• The Opportunity Solution Tree skill encodes five distinct PM frameworks from industry leaders Torres, Olsen, and Savoia.
• Source definitions reside in pm-product-discovery/skills/opportunity-solution-tree/SKILL.md with specific line references to each framework (lines 12-22).
• Opportunity prioritization uses Dan Olsen's mathematical scoring (Importance × [1 − Satisfaction]) at lines 18-19.
• Team structure follows the Product Trio model for solution generation at line 20.
• Validation requires Savoia's skin-in-the-game experiments at line 22 rather than opinion-based decisions.

Frequently Asked Questions

What is the primary file containing the Opportunity Solution Tree framework definitions?

The core definitions are located in pm-product-discovery/skills/opportunity-solution-tree/SKILL.md within the phuryn/pm-skills repository, with specific framework references spanning lines 12-22.

How does the skill prioritize which opportunities to pursue?

The skill applies Dan Olsen's Opportunity Score calculation (Importance multiplied by [1 minus Satisfaction]) as documented at lines 18-19 of the SKILL.md file, enabling data-driven prioritization before solution generation begins.

Which team structure does the skill recommend for generating solutions?

According to line 20 of the skill definition, the Product Trio—comprising the Product Manager, Designer, and Engineer—should collaborate to produce at least three solutions per identified opportunity.

What distinguishes the validation approach in this skill from traditional methods?

The skill mandates Alberto Savoia's "skin-in-the-game" experiments at line 22, requiring real commitment and measurable stakes rather than relying on opinion-based or low-cost validation techniques.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}