product-metrics

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

product-metrics — the Metric Brief

product-metrics — Metric Brief

The gap the old pipeline acknowledged without filling:

product-strategy

demands that "with no metric, the problem is not clear", but no tool helped build that metric — it handed off to a metrics coach that never existed. This is that station: it defines the candidate North Star, builds the tree of levers that hold it up, and gives every active hypothesis a number, a way of measuring it and a value as of today.

旧流程中存在一个被意识到但未填补的缺口：

product-strategy

要求“没有指标，问题就不清晰”，但没有工具辅助构建这些指标——只能交给一个并不存在的指标专家。而本工具就是填补这一缺口的环节：它负责定义候选北极星指标（North Star）、构建支撑该指标的杠杆指标树，并为每个有效假设匹配对应的指标、统计方式及当前数值。

When it is invoked

触发场景

When	From / to
The metric gate of `product-strategy` does not pass ("with no metric, the problem is not clear")	Entry from `product-strategy` ( `.claude/skills/product-strategy/SKILL.md` )
The Metric Brief is written	Exit toward `prd` ( `.claude/skills/prd/SKILL.md` ) — the strategic `context/` of the node is completed with the metric already defined
With no prior gate	Invocable on its own, over the product node already loaded

Both neighboring stations are already installed in this pack: naming them here is real, not invented — unlike the old reference to a metrics coach with neither spec nor owner.

触发时机	来源/去向
`product-strategy` 的指标审核未通过（“没有指标，问题就不清晰”）	从 `product-strategy` 进入（ `.claude/skills/product-strategy/SKILL.md` ）
Metric Brief撰写完成	输出至 `prd` （ `.claude/skills/prd/SKILL.md` ）——节点的战略 `context/` 部分将已定义的指标补充完整
无前置审核环节	可独立调用，基于已加载的产品节点运行

本工具的上下游环节已集成在当前工具包中：此处提及的环节都是真实存在的，而非虚构——不像旧流程中提到的那个既无规范也无负责人的指标专家。

The interview

访谈流程

It is run with the pressure method of

.claude/skills/grill/SKILL.md#method

— cited by path, never copied. The five ingredients (counter-question with an example, pressure capped at 1-2 attempts, escape hatches, evidence hierarchy, every gap recorded) are applied exactly as described there.

Before asking: if the loaded product node has dated research from

product-strategy

(a Discovery Brief with hypotheses), read it — the active hypotheses come from there, they are not asked again. If there is no prior research, they are asked directly.

Four steps, in this order:

采用

.claude/skills/grill/SKILL.md#method

中的施压法执行访谈——通过路径引用，而非复制内容。该方法的五个要素（带有示例的反问、最多1-2次施压、退出机制、证据层级、记录所有缺口）将严格按照原文描述执行。

提问前：如果已加载的产品节点包含来自

product-strategy

的过往研究（带有假设的发现简报），需先阅读这些内容——有效假设将从中提取，无需再次询问。如果没有过往研究，则直接询问相关假设。

访谈分为四个步骤，按以下顺序进行：

1. Candidate North Star

1. 候选北极星指标

A single candidate North Star metric, with the reason in one line: which product decision it moves, not why "it matters". Faced with an answer that names no decision ("because it measures success", "because it is the one everybody looks at"), grill returns it with a counter-question.

确定一个候选北极星指标，并用一句话说明理由：该指标会影响哪项产品决策，而非“为什么重要”。如果得到的答案未提及具体决策（例如“因为它衡量成功”、“因为所有人都关注它”），则通过反问方式退回重新确认。

2. Metric tree

2. 指标树

The North Star on top, its levers below — the variables that, if they move, move the North Star. Every lever carries where it is measured (which event, which table, which source — the where, never how to instrument it: that belongs to the body of the user's product, not to this tool). A lever with no where-it-is-measured is a gap, not a complete line.

将北极星指标放在顶层，下方列出支撑它的杠杆指标——即那些变动会影响北极星指标的变量。每个杠杆指标需明确统计来源（对应哪个事件、数据表或数据源——只需说明来源，无需说明埋点方式：这属于用户产品的核心内容，而非本工具的职责）。未明确统计来源的杠杆指标视为缺口，不构成完整条目。

3. Metric per active hypothesis

3. 每个有效假设对应指标

For each active hypothesis (the ones

product-strategy

brings, or the ones raised here if there is no prior research): which number validates or refutes it, measured how, against what value as of today.

Hard rule: no value with a source, no data. A value as of today that the operator cannot cite with its origin (a dashboard, a measurement, a dated figure) is not written as if they could: it is recorded as a gap, with who closes it — the same gap format

grill

uses. Inventing the number so the row looks complete is the same incomplete scan presented as complete that the rest of the system forbids.

针对每个有效假设（来自

product-strategy

的研究，或无过往研究时在此处提出的假设）：确定验证或推翻该假设的指标、统计方式，以及当前的基准数值。

硬性规则：无来源则无数据。 如果操作人员无法提供当前数值的来源（如仪表盘、测量记录、指定日期的数据），则不能虚构数值填补条目：需将其记录为缺口，并标注负责人——采用与

grill

相同的缺口格式。为了让条目看起来完整而虚构数值的行为，属于系统禁止的“表面完整实则缺失”的操作。

4. Antimetrics

4. 反指标

What should not get worse while the North Star improves, with the threshold that triggers the alarm — a number or a verifiable condition, never "if it gets much worse".

确定在北极星指标提升过程中不应恶化的指标，并设定触发告警的阈值——阈值需为具体数值或可验证的条件，不能是“如果情况大幅恶化”这类模糊描述。

The vanity metric

虚荣指标检查

After every proposed metric (North Star, lever or hypothesis metric), this question is applied: which decision does this number change, in whichever direction it moves?

If there is no answer, or the answer is another metric ("it changes how we see growth"), it is a vanity metric: it is said outright — "this is a vanity metric: it changes no decision" — and the concrete decision the metric should move is requested before accepting it into the Brief. It is neither discarded in silence nor accepted to avoid interrupting the interview.

在每个提出的指标（北极星指标、杠杆指标或假设对应指标）之后，需询问以下问题：无论该数值如何变动，它会改变哪项决策？

如果没有答案，或者答案是另一个指标（例如“它会改变我们对增长的看法”），则该指标属于虚荣指标：需明确指出——“这是虚荣指标：它不会改变任何决策”，并要求提供该指标应影响的具体决策后，才可将其纳入Brief。既不能默默丢弃，也不能为了避免中断访谈而勉强接受。

The Metric Brief

Metric Brief 文档

It closes by writing the deliverable as dated research of the loaded product node, in:

context/<YYYY-MM-DD>-metric-brief.md

Dated, never overwritten — the same criterion the research folder of this repo already uses. The path falls inside

content: orgs/*/products/*/context/*.md

tree.md

: no new glob and no resolver row are needed.

The Brief carries these four sections, in this order, each with its literal heading:

undefined

访谈结束后，将成果作为已加载产品节点的时效性研究文档，写入以下路径：

context/<YYYY-MM-DD>-metric-brief.md

文档带有日期，永不覆盖——与本仓库研究文件夹的现有规范一致。该路径属于

tree.md

中

content: orgs/*/products/*/context/*.md

的范围：无需新增匹配规则或解析条目。

Brief包含以下四个部分，按顺序排列，每个部分使用指定标题：

undefined

Candidate North Star

Metric tree

Metric per hypothesis

Antimetrics


- **Candidate North Star**: the metric and the reason in one line (which decision it moves).
- **Metric tree**: the North Star on top, each lever on one line with its where-it-is-measured.
- **Metric per hypothesis**: one entry per active hypothesis — which number, measured how, value as
  of today or a gap with an owner.
- **Antimetrics**: each one with its alarm threshold.

If the interview detected a vanity metric along the way, the Brief leaves it written anyway —with the
label "(vanity: it does not change [the decision that was asked for and never got an owner, if it
was left unclosed])"— and never deletes it in silence.


- **Candidate North Star**：指标及一句话理由（影响哪项决策）。
- **Metric tree**：顶层为北极星指标，每个杠杆指标单独一行，并标注其统计来源。
- **Metric per hypothesis**：每个有效假设对应一条记录——包含指标、统计方式、当前数值或带负责人的缺口。
- **Antimetrics**：每个反指标及其告警阈值。

如果访谈过程中发现虚荣指标，Brief仍会保留该指标——并标注“（虚荣指标：无法改变[未明确的决策，若缺口未填补则留空]）”——不会默默删除。

What this deliverable does not claim

本成果的免责声明

The Metric Brief neither creates nor demands a new canonical file of the product node: it is dated research, it adds to what is already there, and it neither replaces nor forces re-versioning a live file of the

context/

. If a metrics canonical file were ever needed (a live

metrics.md

that gets overwritten), that decision is approved by the operator — not by this tool.

Metric Brief既不会创建也不会要求生成产品节点的新规范文件：它是时效性研究文档，仅作为现有内容的补充，不会替代或强制更新

context/

中的实时文件。如果未来需要指标规范文件（可覆盖更新的

metrics.md

），该决策需由操作人员批准——而非本工具决定。

Standalone use

独立使用方式

Without a brain, the deliverable is written to a file in the current folder: the process is the same, but nothing is filed into a node, a backlog or a resolver, and no session scan brings it back later. Inside AI First OS the destinations named above are the real ones and this section does not apply.

The rest of the pack installs one skill at a time. Look at

.claude/skills/

first and offer only the ones that are not there — inside AI First OS they are all installed already, so nothing here gets offered:

grill

—

npx skills add pedroromeroluna/ai-first-product-skills --skill grill

prd

—

npx skills add pedroromeroluna/ai-first-product-skills --skill prd

product-strategy

—

npx skills add pedroromeroluna/ai-first-product-skills --skill product-strategy

The whole pack at once:

npx skills add pedroromeroluna/ai-first-product-skills

The system these skills come from is AI First OS —

github.com/pedroromeroluna/ai-first-os

— where they run over a brain instead of over the current folder.

在无AI First OS支撑的情况下，成果将写入当前文件夹的文件中：流程与集成环境一致，但不会归档到节点、待办事项或解析器中，后续也不会通过会话扫描找回。在AI First OS中，上述目标路径均为真实路径，本章节内容不适用。

工具包中的其余技能需逐个安装。请先查看

.claude/skills/

目录，仅安装未存在的技能——在AI First OS中所有技能已预装，因此无需执行以下操作：

grill

—

npx skills add pedroromeroluna/ai-first-product-skills --skill grill

prd

—

npx skills add pedroromeroluna/ai-first-product-skills --skill prd

product-strategy

—

npx skills add pedroromeroluna/ai-first-product-skills --skill product-strategy

一次性安装整个工具包：

npx skills add pedroromeroluna/ai-first-product-skills

。

这些技能源自AI First OS系统——

github.com/pedroromeroluna/ai-first-os

——在该系统中，技能基于核心引擎运行，而非当前文件夹。