Skip to main content
command CX Codex

north-star — Claude Code command: what it does, how to install

Identifies your North Star Metric, validates it against core criteria, and outlines actionable input metrics.

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-marketing-growth@pm-skills
Open on GitHub

What north-star does

The command guides you through structured product discovery. It starts by analyzing the business model and categorizing the product into one of three games: Attention, Transaction, or Productivity. That classification dictates metric design, as a media platform requires different success indicators than a B2B SaaS workflow.

Next, the command drafts two to three metric options and grades each across seven checkpoints. It verifies whether a metric reflects direct customer value, serves as a leading indicator of revenue, stays actionable, and resists manipulation. For the selected metric, it builds a set of MECE input levers assigned to specific teams, alongside counter-metrics that safeguard against Goodhart's Law.

The final output is a Markdown framework containing the validation matrix, an input metric constellation, and explicit anti-patterns. Revenue is deliberately excluded from North Star candidacy because it acts as a lagging indicator rather than a measure of delivered user value.

What it helps with

  • define a reliable North Star Metric for a new product
  • replace misleading vanity metrics like raw DAU with value delivery indicators
  • break down a top-level goal into actionable team-owned input metrics
  • establish counter-metrics to prevent unintended system gaming

Example prompts for the agent

  • /north-star B2B SaaS for team collaboration
  • /north-star Consumer fitness app monetized through subscriptions
  • /north-star Help me fix our North Star — we're tracking DAU but it doesn't feel right

How to install north-star

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-marketing-growth@pm-skills

2Manually: put the files in place

.claude/commands/north-star.md

Call it with /north-star. For all projects use ~/.claude/commands/

Questions about north-star

How to install the north-star command in Claude Code?

Add the marketplace and install the package with /plugin marketplace add phuryn/pm-skills followed by /plugin install pm-marketing-growth@pm-skills. You can also place the command definition directly in .claude/commands/north-star.md.

What does the north-star command do?

It identifies your business model category, proposes candidate metrics, validates them against seven criteria, and produces a Markdown framework with input metrics and counter-metrics.

Why does the command reject revenue as a North Star Metric?

Revenue is a lagging business result rather than a leading signal of user value, making it ineffective for guiding day-to-day product decisions.

Source text

north-star.md · MIT
---
description: Define your North Star Metric and supporting input metrics — classify the business game and validate against best practices
argument-hint: "<product or business>"
---

# /north-star -- North Star Metric Definition

Identify the single metric that best captures the value your product delivers, plus the input metrics that drive it. Classifies your business game and validates against proven criteria.

## Invocation

```
/north-star B2B SaaS for team collaboration
/north-star Consumer fitness app monetized through subscriptions
/north-star Help me fix our North Star — we're tracking DAU but it doesn't feel right
```

## Workflow

### Step 1: Understand the Product

Ask:
- What is the product? What value does it deliver to users?
- What's the business model? (subscription, transaction, advertising, marketplace)
- Current metrics being tracked (if any)
- Why is this needed now? (new product, existing metric feels wrong, team alignment)

### Step 2: Classify the Business Game

Apply the **north-star-metric** skill:

Identify which game the product is playing:
- **Attention**: Revenue from user time/engagement (media, social, ad-supported)
- **Transaction**: Revenue from purchases (e-commerce, marketplace)
- **Productivity**: Revenue from efficiency gains (SaaS, tools, B2B)

The game determines what kind of North Star makes sense.

### Step 3: Define the North Star

- Propose 2-3 North Star candidates
- Validate each against 7 criteria:
  1. Expresses value delivered to customers
  2. Is a leading indicator of revenue
  3. Is measurable and trackable
  4. Is understandable by the whole team
  5. Is actionable (teams can influence it)
  6. Is not a vanity metric
  7. Is not gameable without delivering real value
- Recommend the strongest candidate with rationale

### Step 4: Define Input Metrics

For the selected North Star, identify 3-5 input metrics:
- Each input metric should be a lever that directly drives the North Star
- Each should be ownable by a specific team
- Together, inputs should be MECE in explaining North Star movement

### Step 5: Generate Metrics Framework

```
## North Star Framework: [Product]

**Business Game**: [Attention / Transaction / Productivity]

### North Star Metric
**Metric**: [precise name]
**Definition**: [formula or measurement method]
**Why this metric**: [explains value, leads revenue, is actionable]
**Current value**: [if known]
**Target**: [goal]

### Validation
| Criterion | Pass? | Notes |
|----------|-------|-------|
| Expresses value | [Y/N] | [explanation] |
| Leading indicator | [Y/N] | [explanation] |
| Measurable | [Y/N] | [explanation] |
| Understandable | [Y/N] | [explanation] |
| Actionable | [Y/N] | [explanation] |
| Not vanity | [Y/N] | [explanation] |
| Not gameable | [Y/N] | [explanation] |

### Input Metrics
| Input Metric | Drives North Star By | Owner | Current | Target |
|-------------|---------------------|-------|---------|--------|

### Metrics Constellation
[Visual tree showing North Star → Input Metrics → Team Actions]

### Counter-Metrics
| Metric | Protects Against |
|--------|-----------------|

### Anti-Patterns Avoided
[Why we didn't choose DAU, revenue, or other common but flawed metrics]
```

Save as markdown.

### Step 6: Offer Next Steps

- "Want me to **build a full metrics dashboard** around this?"
- "Should I **create OKRs** based on these metrics?"
- "Want me to **write SQL queries** to compute these metrics?"

## Notes

- The North Star should measure *value delivered*, not just *activity* — "daily active users" is only good if active use = value delivery
- Revenue is never a good North Star — it's a lagging indicator that doesn't capture user value
- Input metrics are what make the framework actionable — without them, the North Star is just a vanity dashboard
- Revisit the North Star annually or when the business model changes significantly
- Counter-metrics prevent Goodhart's Law — when a metric becomes a target, it ceases to be a good metric

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set120

The whole set →
stakeholder-map stakeholder-map — a command that maps stakeholders on a Power × Interest grid and builds a communication plan. Use it when a project affects different groups and you need to ensure each receives the right information at the right time. CX Codex +1 ★ 28,211repo stars battlecard Generates a concise, sales-focused competitive battlecard comparing two products. Useful before prospect calls to align pricing rebuttals and differentiators. CX Codex +1 ★ 28,211repo stars write-stories write-stories is a Claude Code command that turns a feature brief or PRD into backlog items with acceptance criteria. Choose user stories, job stories, or WWA. CX Codex +1 ★ 28,211repo stars analyze-test analyze-test is a Claude Code command that evaluates A/B test results, checks statistical significance and sample size, and recommends whether to ship, extend, or stop. CX Codex +1 ★ 28,211repo stars growth-strategy growth-strategy builds a growth plan from growth loops and GTM motions. Use it when product traction stalls or you need a structured experiment plan. CX Codex +1 ★ 28,211repo stars strategy The /strategy command builds a complete product strategy through a 9-section Canvas: vision, segments, value, trade-offs, metrics, growth, capabilities, and defensibility. CX Codex +1 ★ 28,211repo stars research-users research-users synthesizes research notes, survey exports, and tickets into user personas, behavioral segments, and journey maps. Helpful for PMs evaluating qualitative data. CX Codex +1 ★ 28,211repo stars setup-metrics setup-metrics is a Claude Code command that defines product metrics from a North Star to alert thresholds. It covers feature measurement planning and dashboard reviews. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open