From discover
Orchestrate Opportunity discovery and hypothesis generation through business and user perspectives
npx claudepluginhub shinpr/claude-code-workflows --plugin discoverThis skill uses the workspace's default tool permissions.
**Context**: Discover Opportunities and generate hypotheses by combining business analysis (BMC/VPC/market) with user analysis (JTBD/pains/gains). Outputs Opportunity files and hypothesis files.
Maps opportunities using Teresa Torres' Opportunity Solution Trees to connect business outcomes, customer needs, solutions, and experiments. Use for product gap analysis or solution space exploration.
Guides product discovery: customer interviews, problem mapping, opportunity assessment, prototype testing, and assumption testing to reduce build risks. Activates on mentions of product discovery, customer research, user interviews.
Builds Opportunity Solution Trees, scores opportunities via importance-satisfaction formula, maps JTBD jobs, and fills Lean Canvas for product discovery and prioritization.
Share bugs, ideas, or general feedback.
Context: Discover Opportunities and generate hypotheses by combining business analysis (BMC/VPC/market) with user analysis (JTBD/pains/gains). Outputs Opportunity files and hypothesis files.
Execution Protocol:
[STOP — BLOCKING] marker — present findings and CANNOT proceed until user explicitly confirmsInput (user request / existing code / market opportunity)
↓
1. Context Assessment → Determine starting point
↓
2. Business Context Analysis → BMC/VPC/Market (if needed)
↓
3. User Context Analysis → Personas/JTBD/Journeys
↓
4. Opportunity Identification → [Stop: Opportunity confirmation]
↓
5. Hypothesis Generation → [Stop: Hypothesis review]
↓
Output: Opportunity files + Hypothesis files in docs/discovery/
Input: $ARGUMENTS
Assess the starting point:
| Situation | Action |
|---|---|
| Greenfield (no existing product) | Full business + user analysis |
| Existing codebase | Invoke codebase-analyzer first for objective fact-gathering |
| Specific market opportunity | Focus on market analysis + VPC |
| User feedback / support tickets | Focus on user analysis + journey mapping |
Vision exists (docs/product/vision.md) | Align discovery with Product Outcomes |
When business context is needed, use the business-context skill frameworks:
See business-context skill references/business-model-canvas.md, references/value-proposition-canvas.md, and references/market-analysis.md for detailed frameworks.
Web search: Use WebSearch tool for market research — industry reports, competitor analysis, trend data. Market research benefits from hypothesis context (unlike code analysis).
docs/product/personas/). If no persona files exist, stop and inform the user that persona files are required before discovery can proceedreferences/journey-template.md to visualize pain points and opportunitiesSynthesize business and user analysis into Opportunities:
references/opportunity-template.md[STOP — BLOCKING] Present Opportunities to user for confirmation:
CANNOT proceed to Step 5 until user explicitly confirms, modifies, or rejects Opportunities.
For confirmed Opportunities, generate hypotheses:
references/hypothesis-template.md[STOP — BLOCKING] Present hypotheses to user for review:
CANNOT write files to docs/discovery/ until user explicitly approves.
After user approval:
docs/discovery/opportunities/docs/discovery/hypotheses/docs/discovery/journeys/ (if created)docs/discovery/INDEX.md| Agent | When | Why (context separation benefit) |
|---|---|---|
| codebase-analyzer (via Agent tool, subagent_type: "discover:codebase-analyzer") | Existing codebase exists | Objective fact-gathering without hypothesis bias |
Included: Opportunity discovery, hypothesis generation, market research, journey mapping Not included: Hypothesis validation, PRD creation, persona deep-dive
docs/discovery/