shipkit-product-definitionlisted

# shipkit-product-definition — Product Blueprint Defines WHAT we build to solve discovered user needs. Reads product-discovery.json (pain points, personas, opportunities) and produces a product blueprint: features, UX patterns, and differentiators. This is the product blueprint — it defines the user-facing solution. The technical approach (mechanisms, design decisions, stack) is handled by `/shipkit-engineering-definition`. Feature phasing (what to build now vs. later) is handled by `/shipkit-product-goals` through stage gates. --- ## When to Invoke **User triggers**: - "What should we build?", "Define features", "Product definition" - "UX patterns", "Differentiators", "What to build" - "Solution design", "Product blueprint" **Workflow position**: - After `/shipkit-product-discovery` (needs discovered user needs) - Before `/shipkit-engineering-definition` (engineering designs mechanisms for these features) - Before `/shipkit-product-goals` (goals derive criteria from features and mechanisms) --- ## Prerequisites **Required** (fail gracefully if missing): - `.shipkit/product-discovery.json` — who the users are and what they need **Recommended** (enrich the proposal): - `.shipkit/why.json` — project purpose and vision - `.shipkit/goals/strategic.json` — project stage and constraints **Optional** (for existing projects): - `.shipkit/stack.json` — technology constraints (informs feasibility) - `.shipkit/codebase-index.json` — what already exists If product-discovery.j