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 --- ## 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**: - Early Pillar 1 (Vision) or Pillar 3 (Co-design) - before specification - Replaces separate prod-personas + prod-jobs-to-be-done + prod-user-stories for POC/MVP --- ## Prerequisites **Optional**: - `.shipkit/why.json` (Vision helps guide persona creation) - `.shipkit/stack.json` (Technical constraints inform feasibility) **If missing**: Generate personas and stories based on user input alone --- ## Process ### Step 0: Check for Existing File > **Fork context — no user prompts.** You are dispatched in a fork and have no user channel. Skip the file-exists menu entirely. 1. Check if `.shipkit/product-discovery.json` exists 2. If exists: read `.shipkit/reviews/direction-assessment.json` if present. If the latest review lists a gap against this artifact, archive the existing file to `.shipkit/.archive/product-discovery.YYYY-MM-DD.json` and regenerate addressing the gap. Otherwise, read the existing file and exit early with a "no changes needed" report — the reviewer already accepted it. 3. If no file exists: proceed to Step 0b (propose mode). --- ### Step