success-criteria-metrics

Define measurable success criteria, guardrails, and decision thresholds before work begins.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Zhachory1/autopraxis --skill success-criteria-metrics-zhachory1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: success-criteria-metrics
Source: https://github.com/Zhachory1/autopraxis/tree/main/skills/success-criteria-metrics
Command: npx skills add https://github.com/Zhachory1/autopraxis --skill success-criteria-metrics-zhachory1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start projects without agreeing on what success looks like, then cherry-pick favorable metrics after seeing results. This Skill locks in a primary metric, guardrails, baselines, and decision rules before execution so outcomes can be judged objectively. ## Core Features & Use Cases - Primary Metric Definition: Select one deciding metric with baseline, target, source, and an explicit decision rule instead of a dashboard of competing numbers. - Guardrails and Anti-Metric-Shopping Lock: Add safety, cost, latency, and quality constraints, and require human approval before any post-result metric change. - Measurement Plan and Gate Status: Specify instrumentation, evaluation windows, and confidence tolerances, then emit a ready/blocked gate verdict with telemetry. - Use Case: Before launching an ML experiment, use this Skill to lock an offline/online primary metric, set guardrails for latency and fairness, and define the pass/fail threshold so the launch decision cannot be relitigated after results arrive. ## Quick Start Define success criteria and guardrail metrics for my upcoming feature launch, including a baseline, target, and decision rule.

Frequently Asked Questions about success-criteria-metrics

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

FAQPage Schema
How do I define success metrics for a product launch?▼

Choose one primary metric tied to a user or business outcome, record its baseline and target, and write an explicit decision rule for pass or fail. Add guardrail metrics for safety, cost, and quality so a win on the primary metric cannot hide harm elsewhere.

How to set offline and online metrics for ML experiments?▼

Pick a primary metric and link its offline proxy to the online outcome, stating when the proxy becomes invalid. Define the evaluation window, confidence tolerance, and minimum detectable effect before running the experiment.

What is metric shopping and how do I prevent it?▼

Metric shopping is selecting favorable metrics after seeing results. Prevent it by locking the primary metric and decision rule before execution, listing exploratory metrics separately, and requiring human approval for any post-result metric change.

What is the difference between a primary metric and a guardrail metric?▼

The primary metric drives the decision and has a target and decision rule. Guardrails are constraints such as latency, cost, or reliability with thresholds and failure actions that block a harmful win.

When should a metrics gate be marked not ready?▼

Mark the gate needs-instrumentation when the baseline or data source is missing, and needs-human-decision when thresholds cannot be agreed. A metric without a documented baseline or feasible measurement method cannot gate work.