← ClaudeAtlas

discoverylisted

Use when the user proposes a feature or product idea with no plan yet, asks whether something is worth building, to challenge a feature, compare with existing products or competitors, run a market scan, or write an opportunity brief. Also use when the user mentions product discovery, build versus buy, PR-FAQ, or jobs to be done.
itsaspacestation/natural-intelligence · ★ 2 · Web & Frontend · score 73
Install: claude install-skill itsaspacestation/natural-intelligence
# Discovery ## When to use - User proposes a feature or product idea and no workspace or plan exists - User asks whether something is worth building, or to challenge a feature - User asks what already exists: competitors, alternatives, build versus buy - User asks for an opportunity brief, a PR-FAQ, or a market scan ## Overview Discovery decides whether and what to build. Planning decides how. The job is killing risk before engineering commits, so a day spent deciding not to build is a win, never a failure. The output is a one-page opportunity brief ending in a verdict: build, buy, test first, or drop. On build, the [`plan`](../plan/SKILL.md) skill takes over. Reference: [market-scan.md](market-scan.md). Read it at workflow step 3. ## Workflow 1. **Reframe as an outcome.** Rewrite the request as the user or business outcome it serves, measurable in one sentence. A feature with no stated outcome is the first red flag: ask one question, or in a delegated context derive the outcome from the brief and record it as an assumption. 2. **Challenge the four big risks** (Cagan, *Inspired*): **value** (will anyone use it), **usability** (can they figure it out), **feasibility** (can we build it in the time we have), **viability** (does it work for the business: cost, legal, support). One sentence per risk, each marked `low`, `open`, or `blocking`, with its evidence. 3. **Scan the market.** Browse what already solves the job: competitors, adjacent products,