success-metrics

Define metric stacks with primary, counter, guardrail, and leading indicators.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/argen/hornero --skill success-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: success-metrics
Source: https://github.com/argen/hornero/tree/main/roles/product-manager/skills/success-metrics
Command: npx skills add https://github.com/argen/hornero --skill success-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps product managers define and communicate success metrics before development, ensuring alignment and preventing metric gaming.

Core Features & Use Cases

  • Metric Design: Craft a metric stack with a primary, counter, guardrail, and leading indicators.
  • Four-Risk Framing: Apply a framework to address value, usability, feasibility, and business viability risks.
  • OKR Alignment: Use the discipline of Objectives and Key Results to shape success criteria.
  • Leading Indicators: Identify input metrics that predict primary metric outcomes.
  • Guardrails: Set boundaries to protect adjacent system health.

Quick Start

Define the success metrics for your upcoming feature launch with the success-metrics skill.

Frequently Asked Questions about success-metrics

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

FAQPage Schema
How do I design success metrics for a product feature launch?

Define success metrics by building a comprehensive stack containing a primary metric, counter metrics, guardrails, and leading indicators. This framework aligns your feature launch with product strategy and ensures data-driven decision-making.

How do I align OKRs with product strategy to prevent metric gaming?

Align OKRs with product strategy by using them to shape success criteria alongside a metric stack. Incorporating counter metrics and guardrails sets strict boundaries that protect adjacent system health and prevents metric gaming.

What are guardrail metrics and when do I need them for data-driven decision-making?

Guardrail metrics are boundaries set to protect adjacent system health during feature launches. You need them during metric design to ensure that improving your primary metric does not negatively impact other critical areas of the product.

How do I apply a four-risk framework to product metric design?

Apply the four-risk framing to metric design by addressing value, usability, feasibility, and business viability risks. This framework helps identify leading indicators and counter metrics that comprehensively mitigate product risks before launch.

How do I identify leading indicators for my product metrics?

Identify leading indicators by selecting input metrics that predict primary metric outcomes within your metric stack. This requires understanding product risk and metrics design to ensure these early signals align with your overall product strategy.

What is the best way to define a metric stack for a quarterly product launch?

The best way to define a metric stack for a quarterly launch is to combine a primary metric with counter metrics, guardrails, and leading indicators. This comprehensive approach aligns with product strategy and supports data-driven decision-making across the quarter.