shipkit-product-discoverylisted

# shipkit-product-discovery - Lightweight Product Discovery **Purpose**: Combines personas, user journey mapping, and user stories into a single lightweight workflow for POC/MVP projects **Protocol:** This skill follows the canonical elicitation protocol defined in `install/shared/references/elicitation-protocol.md` (the *mechanics* — marker, state files, resume). The steps below are this skill's specific application of that protocol. **Calibration:** Apply `install/shared/references/ground-or-ask-calibration.md` (the *intelligence* — propose vs ask). **Ground first:** scan cited signals (the opening prompt, `why.json`, `README.md`, `package.json`, the codebase) before asking anything. Propose every field you can tie to a signal, tagged with its source; flag low-leverage guesses as `guessed`. **High-leverage for this skill:** who the PRIMARY personas are and their core journeys / top user needs — these define who the product is FOR and are hard to reverse. If ungrounded, ask. **Low-leverage:** secondary personas, edge-case journeys, ordering details — propose flagged defaults, don't ask. Target 2–3 questions maximum; if you're about to ask more, your grounding pass was too shallow. Never silently invent an ungrounded primary persona or core need. --- ## When to Invoke **User triggers**: - "Who are our users?", "Create personas", "User research" - "User journey", "Map user needs", "Product discovery" - "User stories", "What features?", "Requirements" **Workflow position