product-discovery
Product Discovery
Figure out whether an idea is worth building before you commit engineering time. The goal is sufficient evidence that the solution will work — not certainty, but enough to bet responsibly.
70-90% of features built without validation fail to deliver business results. Discovery exists to catch the failures early and cheap, so engineering investment goes toward ideas with real evidence behind them.
Core Principle
Every idea tested in discovery should cost at least one order of magnitude less than building the real thing. If engineering a feature takes 4 weeks, discovery should take days. If it takes months, discovery should take weeks.
Process
- Understand the idea
- Assess the four product risks
- Identify what you don't know
- Design experiments
- Define evidence gates
- Write the discovery plan
More from teambrilliant/dev-skills
implementation-planning
>-
11implement-change
>-
10product-thinker
>-
10shaping-work
Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea that needs to become a concrete work definition — feature requests, bug reports, PRDs, customer feedback, Slack threads, stakeholder asks, or vague "we should do X" statements. Trigger phrases include "shape this", "scope this", "write a PRD", "define this work", "turn this into a ticket", "flesh this out", "spec this out", "what should we build for X", "I have an idea for...", or any rough input that needs structure before implementation can begin.
9qa-test
Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser", "verify the feature", "qa test", "browser test", or after completing an /implement-change to verify acceptance criteria in a real browser. Opens Chrome via MCP, exercises each acceptance criterion, verifies via DOM snapshots, and reports pass/fail. The "closer" for every implementation — proof it works, not just that tests pass.
8systems-decomposition
Break down complex products, features, or systems into fundamental primitives and building blocks. Use when someone says "break down X", "decompose this", "what are the primitives for Y", "building blocks of Z", or needs to understand a complex system from first principles. Outputs human-readable lists with ASCII diagrams showing relationships.
7