shipkit-product-goalslisted

# shipkit-product-goals — Product Success Criteria **Purpose**: Derive measurable user-outcome criteria from the product blueprint. Each feature, UX pattern, and differentiator implies criteria for "how do we know this works?" — this skill makes those criteria explicit, measurable, and trackable. **What it does**: Reads the product blueprint + discovery context + stage from strategic.json, proposes user-outcome criteria (P-*), appends P-* IDs to existing stage gates, then writes `goals/product.json`. **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:** This is a DERIVATION skill — the vast majority of P-* criterion fields are directly derivable from cited upstream artifacts (`product-definition.json`, `product-discovery.json`, `goals/strategic.json`). Propose every criterion you can ground, tagged with its source; flag low-leverage guesses as `guessed`. The only genuinely **high-leverage ungrounded** fields are the **concrete numeric thresholds** (e.g., "> 80% completion rate") when no signal from stage calibration, prior metrics, or product-definition implies a specific value. Ask those — and only those. Keep the question set tiny (often zer