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
- AntonioMellies/claude-code-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AntonioMellies/claude-code-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- agent-memory-designerSkill
- ai-cost-optimizerSkill
- ai-evaluation-builderSkill
- ai-latency-optimizerSkill
- ai-solution-architectSkill
- ai-workflow-builderSkill
- context-engineeringSkill
- human-in-the-loop-designerSkill
- multi-agent-plannerSkill
- prompt-engineerSkill
- prompt-optimizerSkill
- prompt-reviewerSkill
- adr-generatorSkill
- api-designerSkill
- architecture-reviewSkill
- component-diagram-builderSkill
- container-diagram-builderSkill
- data-flow-analyzerSkill
- integration-plannerSkill
- observability-plannerSkill
- scalability-advisorSkill
- solution-architectureSkill
- system-context-builderSkill
- experiment-designerSkill
- go-to-market-plannerSkill
- pricing-strategy-advisorSkill
- mcp-best-practicesSkill
- mcp-client-generatorSkill
- mcp-security-reviewSkill
- mcp-server-generatorSkill
- mcp-tool-generatorSkill
- acceptance-criteria-generatorSkill
- analytics-instrumentation-plannerSkill
- competitive-analysisSkill
- epic-generatorSkill
- feature-prioritizationSkill
- idea-validatorSkill
- north-star-metric-advisorSkill
- okr-builderSkill
- persona-generatorSkill
- prd-generatorSkill
- problem-statement-builderSkill
- product-vision-builderSkill
- sprint-plannerSkill
- story-mappingSkill
- user-story-generatorSkill
- value-proposition-designerSkill
- chunking-strategy-advisorSkill
- embedding-strategy-advisorSkill
- hybrid-search-advisorSkill
- knowledge-ingestion-plannerSkill
- rag-architecture-designerSkill
- retriever-optimizerSkill
- ai-governance-advisorSkill
- ai-threat-modelingSkill
- guardrails-builderSkill
- owasp-llm-reviewerSkill
- prompt-injection-detectorSkill
- skill-nameSkill
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
- Distinctive: line 66
Prefer interviews, prototypes, concierge tests over builds.
- Distinctive: line 110
Use Teresa Torres' Opportunity Solution Tree structure.
≈ “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.
Files
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):
| ID | Opportunity | Evidence | Impact estimate |
Opportunities are problems, not solutions.
Step 3: Prioritize opportunities
Score using impact × evidence confidence:
| Opportunity | Impact (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:
| Opportunity | Solution | Assumption | Cheapest test |
Solutions are hypotheses, not commitments.
Step 5: Design discovery experiments
| Experiment | Tests | Method | Timeline | Success criteria |
Prefer interviews, prototypes, concierge tests over builds.
Step 6: Validate
Run Validation checklist.
Decision Rules
| Condition | Action |
| Outcome not measurable | Stop; define metric or run product-vision-builder |
| Opportunities are solutions | Reframe as underlying customer problems |
| No evidence for any opportunity | Mark all as assumptions; prioritize cheapest tests |
| >10 opportunities | Cluster into themes; prioritize within themes |
| Experiment requires >2 weeks | Propose 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
| Outcome | Recommended Skill |
| Validate specific idea | product/idea-validator |
| Define problem statement | product/problem-statement-builder |
| Set team goals | product/okr-builder |
| Prioritize solutions | product/feature-prioritization |
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
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.

