shipkit-why-projectlisted

# shipkit-why-project - Project Vision & Strategy **Purpose**: Create a strategic overview that answers: Who is this for? What problem does it solve? Where are we? Where are we going? How are we getting there? What are we NOT building? **What it does**: Collects core vision inputs, generates `.shipkit/why.json`, provides strategic context for all future sessions. **Protocol:** This skill follows the canonical elicitation protocol defined in `install/shared/references/elicitation-protocol.md`. The steps below are this skill's specific application of that protocol. --- ## When to Invoke **User triggers**: - "Define the project vision" - "Why are we building this?" - "What's this project about?" - "Create project overview" **Auto-suggested**: Session start if `why.json` doesn't exist (via shipkit-session-start.py) --- ## Prerequisites **None** - This can be the first skill you run (even before shipkit-project-context) **Recommended order:** 1. `/shipkit-why-project` - Define strategic vision 2. `/shipkit-stage` - Set project stage, constraints, and business metrics 3. `/shipkit-product-discovery` - Define personas & user needs 4. `/shipkit-product-definition` - Design solution blueprint 5. `/shipkit-product-goals` - Define user-outcome success criteria (P-*) --- ## Process ### Step 0: Context Shortcut Before checking elicitation state, attempt a context-based shortcut: 1. Read available context: `README.md`, `package.json` (name, description, keywords), existing