One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill ost-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ost
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/ost
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill ost-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often jump from brainstorming straight to solutions without grounding decisions in research. This Skill structures discovery work into an Opportunity Solution Tree where every opportunity is backed by cited evidence, preventing solution-first thinking and unsupported roadmap bets. ## Core Features & Use Cases - Evidence-Based Opportunity Mapping: Extracts opportunities from interview transcripts, analytics, and observation notes, requiring at least two evidence citations per opportunity. - Structured Solution Generation: Generates multiple solution hypotheses per leaf opportunity, framed as Lean UX hypotheses and assessed against the Four Risks (value, usability, feasibility, viability). - Continuous Tree Maintenance: Updates existing trees with new research, prunes invalidated solutions, and refreshes confidence scores weekly. - Use Case: After completing a round of user interviews, feed the transcripts into this Skill to produce a hierarchical tree linking your north star outcome to validated opportunities and testable solution experiments. ## Quick Start Use the ost skill to build an Opportunity Solution Tree from my user interview transcripts with the outcome of increasing onboarding completion.

Frequently Asked Questions about ost

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

FAQPage Schema
How do I build an Opportunity Solution Tree from user research?▼

Start with a desired outcome tied to your north star metric, then extract opportunities from interview transcripts and behavioral data. Each opportunity must cite at least two evidence sources and be phrased as a user need, not a solution.

What is the difference between an opportunity and a solution in an OST?▼

Opportunities are unmet user needs, pain points, or desires discovered from research evidence. Solutions are ideas generated afterward to address validated opportunities, and each solution should be framed as a testable Lean UX hypothesis.

Can I use an OST without user interview data?▼

No. This Skill explicitly forbids brainstorming opportunities; every opportunity must link to at least two research data points. If no interview data exists for an opportunity, it is flagged as an evidence gap rather than included.

How often should an Opportunity Solution Tree be updated?▼

The OST is a living document that should be updated weekly with new research. Updates include adding evidence-backed opportunities, refining unsupported ones, generating new solutions, and pruning invalidated solutions.

What are the Four Risks in product discovery?▼

The Four Risks are value, usability, feasibility, and viability, drawn from the Torres Product Trio framework. Each solution in the tree is assessed against all four dimensions, and each risk requires its own independent evidence.