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 *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:** propose every vision field you can tie to a cited signal (the opening prompt, README, codebase, package.json), tagged with its source; flag low-leverage guesses as `guessed`. Only the genuinely-unknown **high-leverage** fields (who it's for, the core problem, the one-way-door constraints) become `NEEDS_ELICITATION` questions. Do not ask what a signal already answers; do not silently invent a high-leverage field. Runs autonomous (propose + few questions) by default; interactive when signals are thin. --- ## 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 shipk