agentleFS
patonkikhpatonkikh/APES/skills/product/product-discovery-assistant/skill.md

product-discovery-assistant

Skill3 starsChanged 4 months agoMITView on GitHub

Facilitate structured product discovery using Opportunity Solution Tree (OST) and Teresa Torres framework: map outcomes, opportunities, solutions, and experiments. Use when working on product discovery, PRDs, user stories, OKRs, or backlog planning.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer interviews, prototypes, concierge tests over builds.

    line 66
  2. Distinctive:

    Use Teresa Torres' Opportunity Solution Tree structure.

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Product Discovery Assistant

Purpose

Facilitate structured product discovery using Opportunity Solution Tree (OST) and Teresa Torres framework: map outcomes, opportunities, solutions, and experiments.

Input: Product outcome goal, existing research (optional), team constraints
Output: Discovery board with opportunity tree, prioritized opportunities, and experiment backlog Examples: See examples.md for worked input/output.


Workflow

Step 1: Define desired outcome

Specify:

  • Business/product outcome (measurable)
  • Time horizon
  • Success metric from product vision or OKRs

Format: "Increase [metric] from [baseline] to [target] by [date]."

Step 2: Map opportunities

Brainstorm and structure opportunities (customer problems/needs):

IDOpportunityEvidenceImpact estimate

Opportunities are problems, not solutions.

Step 3: Prioritize opportunities

Score using impact × evidence confidence:

OpportunityImpact (1-5)Evidence (1-5)Score

Select top 3 for solution exploration.

Step 4: Generate solution options

For each top opportunity, list 2–3 solution ideas:

OpportunitySolutionAssumptionCheapest test

Solutions are hypotheses, not commitments.

Step 5: Design discovery experiments

ExperimentTestsMethodTimelineSuccess criteria

Prefer interviews, prototypes, concierge tests over builds.

Step 6: Validate

Run Validation checklist.


Decision Rules

ConditionAction
Outcome not measurableStop; define metric or run product-vision-builder
Opportunities are solutionsReframe as underlying customer problems
No evidence for any opportunityMark all as assumptions; prioritize cheapest tests
>10 opportunitiesCluster into themes; prioritize within themes
Experiment requires >2 weeksPropose smaller test first

Validation

  • Outcome stated with metric, baseline, target
  • ≥5 opportunities listed as problems (not solutions)
  • Top 3 opportunities prioritized with rationale
  • ≥2 solutions per top opportunity
  • ≥3 experiments with success criteria
  • Experiments are cheaper than building full solutions
  • No committed roadmap — discovery artifacts only

Anti-patterns

  • Solution-first discovery — jumping to features before understanding opportunities.
  • Fake evidence — marking assumptions as validated without data.
  • Analysis paralysis — endless research without experiments.
  • Outcome = output — "ship feature X" instead of business outcome.
  • Skipping assumption mapping — experiments that don't test specific assumptions.

Best Practices

  • Use Teresa Torres' Opportunity Solution Tree structure.
  • One outcome per discovery cycle.
  • Interview 5–8 customers per opportunity cluster.
  • Time-box discovery sprints (2 weeks).
  • Link to idea-validator for assumption testing.

Output Structure

# Product Discovery: [Outcome Name]

## Desired Outcome
[Metric, baseline, target, horizon]

## Opportunity Tree
| ID | Opportunity | Evidence | Impact |
|----|-------------|----------|--------|

## Top Opportunities (prioritized)
1. [Opportunity] — score: X

## Solution Options
| Opportunity | Solution | Assumption to test |
|-------------|----------|-------------------|

## Experiment Backlog
| # | Experiment | Tests assumption | Method | Timeline | Success |
|---|------------|------------------|--------|----------|---------|

## Next Review
[Date and criteria to continue/stop discovery]

Next Skills

OutcomeRecommended Skill
Validate specific ideaproduct/idea-validator
Define problem statementproduct/problem-statement-builder
Set team goalsproduct/okr-builder
Prioritize solutionsproduct/feature-prioritization

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.