What problem does it solve? Product managers often pick vague or vanity metrics that cannot detect whether a feature actually worked. This Skill guides you through selecting a primary metric, guardrail metrics, and kill criteria that pass the six STEDII criteria (Sensitive, Timely, Easy to understand, Directional, Implementable, Independent), grounded in your existing PRDs, business context, and historical baselines. ## Core Features & Use Cases - STEDII Metric Validation: Evaluates every proposed metric against six criteria with explicit pass/fail reasoning. - Context-Aware Baselines: Automatically pulls feature context from PRDs, business info, historical metrics, strategy docs, and meeting notes before proposing targets. - Structured Output Template: Produces a metrics definition with primary metric, baseline, target, guardrails with acceptable ranges, kill criteria, and a measurement plan. - Use Case: Before launching an A/B test for a new onboarding flow, run this Skill to define activation rate as the primary metric, set page load time and error rate as guardrails, and establish rollback thresholds. ## Quick Start Ask the assistant to define success metrics for your feature using the STEDII framework, providing the feature name, the user behavior it changes, and the expected business outcome.
