define-north-star

Define and validate a North Star Metric aligned with business model and retention drivers.

1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/zacgoodwin/AIBootstrap --skill define-north-star-zacgoodwin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-north-star
Source: https://github.com/zacgoodwin/AIBootstrap/tree/main/.claude/skills/define-north-star
Command: npx skills add https://github.com/zacgoodwin/AIBootstrap --skill define-north-star-zacgoodwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often track scattered or vanity metrics that fail to align strategy, prioritize work, or predict retention and revenue. This Skill guides you through identifying, validating, and operationalizing a North Star Metric grounded in your business model. ## Core Features & Use Cases - North Star Definition: Works through Core Value identification, the Frequency x Core Action x Breadth formula, and validation tests to produce a candidate metric. - Validation & Guardrails: Applies measurable, actionable, leading-indicator, and tradeoff tests, plus 2-3 guardrail metrics with thresholds and breach actions. - Input Metric Driver Tree: Breaks the North Star into team-owned input metrics and outputs a structured analysis to outputs/analyses/north-star-[quarter].md. - Use Case: A Series A SaaS team unsure whether to optimize signups or activation uses the Skill to evaluate retention data, select "Weekly Active Teams" as their North Star, and define guardrails for NPS and CAC. ## Quick Start Ask the assistant to help you define or validate your North Star metric using your business model and retention data.

Frequently Asked Questions about define-north-star

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

FAQPage Schema
How do I define a North Star Metric for my product?

Identify your core value, find the user action most correlated with retention, then combine Frequency, Core Action, and Breadth into a formula. Validate it against measurability, actionability, and leading-indicator tests before adoption.

What is a good North Star Metric for SaaS products?

Common SaaS North Stars include Weekly Active Users engaging with the core feature, active users per account, or payment volume processed. The right choice depends on your business model, growth stage, and which action best predicts retention.

Does every product need a single North Star Metric?

No. Marketplaces, multi-product companies, and complex B2B products often mislead teams with one metric. A constellation of 2-4 metrics works better when optimizing one number would harm another side of the business.

Why is revenue a bad North Star Metric?

Revenue is a lagging outcome, not a value metric. It can rise while product value declines through price increases, and it responds too slowly to guide weekly product decisions. Use a value-delivery metric with revenue as a guardrail instead.

What guardrail metrics should accompany a North Star?

Define 2-3 guardrails covering quality (NPS, support volume), monetization (ARPU, LTV), and efficiency (CAC, cost per transaction). Set floor thresholds with defined breach actions, and review them quarterly.

When should I change my North Star Metric?

Revisit every 6-12 months or at major stage transitions such as moving from growth to monetization. Changing it quarterly causes team whiplash, while never evolving it leaves the metric misaligned with company maturity.