product-discoverylisted

# Product Discovery — how top product teams operate Backs the `product-manager` agent and the PRD/brainstorm/change stages. Pairs with `prd-authoring`, `platform-blueprint`, and `accessibility-wcag`. User > skills > default. ## Fits in the pipeline Stage 0 (discover), Stage 1 (PRD/brainstorm), Stage 9 (change requests). Outcomes feed Stage 3+. ## Continuous discovery - Interview customers **weekly and continuously** — never a one-time upfront phase. Discovery and delivery run in parallel (**dual-track**). - Use **opportunity-solution trees**: a single controllable **outcome** at the root → **opportunities** (real customer needs/pains, gathered via story-based prompts "tell me about a time when…") → **solutions** → **assumption tests**. Limit WIP: one opportunity at a time; advance **~3 solutions** and compare by testing their riskiest assumptions, never one idea in isolation. - Source: https://www.producttalk.org/opportunity-solution-trees/ ## PRD / spec (working-backwards) - Separate **problem from solution**; spend disproportionate effort on the problem. Include: problem/background, **target user (never "everyone")**, goals, **non-goals (explicit scope-out)**, **success metrics**, requirements, risks, open questions. Favor a tight **1-pager**. - For new products/major bets, use **Amazon Working Backwards**: write the **fictional press release first** (customer POV) + an **FAQ** (external: how/price/support; internal: finance/legal/risk). Treat the PR-FAQ