feature-metrics

Define experiment metrics using the STEDII framework for product features.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TimothyNguyen04/pmos --skill feature-metrics-timothynguyen04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-metrics
Source: https://github.com/TimothyNguyen04/pmos/tree/main/PM-OS/.claude/skills/feature-metrics
Command: npx skills add https://github.com/TimothyNguyen04/pmos --skill feature-metrics-timothynguyen04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product managers and teams define clear, measurable, and trustworthy success metrics for new features using the STEDII framework, ensuring experiments are well-defined and results are interpretable.

Core Features & Use Cases

  • Metric Definition: Guides users through defining primary metrics, guardrail metrics, and kill criteria.
  • Framework Application: Enforces the use of the STEDII (Sensitive, Timely, Easy to Understand, Directional, Implementable, Independent) framework for metric quality.
  • Contextualization: Integrates with existing product documents, business information, and historical data for informed metric selection.
  • Use Case: When launching a new user onboarding flow, use this skill to define the primary success metric (e.g., onboarding completion rate) and guardrail metrics (e.g., page load time, error rates) to ensure the feature is successful without causing negative side effects.

Quick Start

Use the feature-metrics skill to define success metrics for your new feature.

Frequently Asked Questions about feature-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define success metrics for a product feature experiment?

Define success metrics for a product feature experiment using the STEDII framework to ensure your metrics are sensitive, timely, easy to understand, directional, implementable, and independent. This guarantees experiment results are well-defined and interpretable.

What is the STEDII framework for product metrics?

The STEDII framework for product metrics is a quality validation structure ensuring your experiment metrics are Sensitive, Timely, Easy to Understand, Directional, Implementable, and Independent. It guides the selection of primary metrics, guardrail metrics, and kill criteria.

How do I set up guardrail metrics and kill criteria for feature launches?

Set up guardrail metrics and kill criteria for feature launches by analyzing product context, business information, and historical data. This ensures the feature is successful without causing negative side effects like increased error rates or page load delays.

Can I use existing product documents to inform experiment metric selection?

You can use existing product documents to inform experiment metric selection by integrating business information and historical data into the STEDII framework. This contextualization facilitates the selection of trustworthy primary metrics and guardrails.

When should I use primary metrics versus guardrail metrics in product management?

Use primary metrics versus guardrail metrics in product management when you need to measure the main success of a feature, while guardrails ensure no negative side effects occur. Defining both using the STEDII framework ensures trustworthy experimentation.