product-discovery

Use when the product problem, target user, value loop, or MVP is unclear; turn an idea into evidence-seeking assumptions and a smallest useful product outcome before implementation.

SKILL.md

GitHub

Product Discovery

  1. Identify the concrete user, context, current workaround, pain, and desired outcome.
  2. Separate facts, assumptions, and unknowns.
  3. Define the smallest end-to-end value loop a user can actually complete.
  4. Identify the riskiest assumption and the cheapest way to test it.
  5. Avoid feature inventories. Prefer one useful workflow over many disconnected screens.
  6. Convert the approved outcome into task acceptance criteria and measurable failure behavior.
  7. Do not block low-risk implementation on ceremonial research when the problem is already evidenced.