Part of Forge DevKit ecosystem
◇ forge-discovery
Validate before you build
The problem
Building features nobody asked for
Pendo/ProductPlan data shows the average SaaS app has 45% of features never clicked. Discovery prevents building what nobody asked for.
Assumptions disguised as requirements
Teams ship based on gut feelings. No evidence, no interviews, no validation.
Discovery artifacts disconnect from development
Research lives in Google Docs. Development starts from scratch. Insights never reach the codebase.
How it works
Install
One command adds forge-discovery to your environment.
Configure
3-gate wizard detects your product type and recommends discovery methods.
Discover
Guided ideation, competitive research, problem validation, and interview synthesis.
Feed downstream
Discovery artifacts flow into forge-marketing and forge-product automatically.
Key capabilities
◇4 discovery modes
Ideate (diverge), research (competitive landscape), validate (evidence-test assumptions), interview (extract user patterns). Each output feeds the next.
◇7 psychology biases
Contextual warnings at decision points. Prevents confirmation bias, survivorship bias, and more.
◇Competitive landscape mapping
Structured competitor analysis with positioning gaps and opportunity identification - so you build differentiators, not clones.
◇Interview synthesis
Extract patterns from user interviews. Evidence-based insights, not cherry-picked quotes.
Sample output
A real-world example of what this module produces.
◆ Validation Hypothesis #3
Belief: Freelancers will pay for automated invoice reminders
Signal: 70% of survey respondents chase payments manually
Test Design:
Method: Fake-door test on taskflow-app pricing page
Audience: 200 existing free-tier users
Duration: 7 days
Pass if: >= 15% click "Upgrade for reminders"
Fail if: < 5% click rate
Bias check: Confirmation bias - also track "not interested" reasonsWho is this for
Founder
Validate product ideas with structured research before committing development resources.
Product Manager
Run evidence-based discovery with bias protection instead of gut-feel prioritization.
UX Researcher
Synthesize interview patterns and competitive insights into actionable product specs.
forge-discovery vs Manual product discovery
| Dimension | Manual product discovery | Forge DevKit |
|---|---|---|
| Structure | Freeform notes in Google Docs | Structured artifacts with downstream connections |
| Bias protection | None - you bring your own biases | 7 cognitive bias detectors at decision points |
| Development connection | Manual translation to specs | Artifacts feed forge-marketing and forge-product directly |