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-*), lets user validate, appends P-* IDs to existing stage gates, then writes `goals/product.json`. **Output**: One JSON file: - `goals/product.json` — User-outcome criteria (PM owns) > **Strategic goals** (stage, constraints, business metrics: S-*) are handled by `/shipkit-stage`, owned by the Visionary agent. > **Engineering goals** (technical performance: E-*) are handled by `/shipkit-engineering-goals`, owned by the Architect agent. --- ## Modes | Mode | Trigger | What It Does | |------|---------|-------------| | **Define** (default) | "Set goals", "success criteria", "product goals" | Derive P-* criteria from product blueprint, write product.json, append P-* to gates | | **Evaluate** | `--evaluate`, "check metrics" | Read metrics/latest.json, compare product criteria to targets, output gap report | --- ## When to Invoke **User triggers**: - "Define success criteria", "How do we measure success?" - "Set product goals", "What are our goals?" - "Evaluate goals", "Check metrics" **Workflow position**: - After `/shipkit-product-definition` (reads