Create Metrics Framework

Overview

Build a metrics framework combining the North Star Framework (Amplitude), AARRR Pirate Metrics, and HEART Framework (Google). Defines one North Star metric, the input metrics that drive it, and guardrail metrics that prevent gaming. Gives the team a shared definition of success.

Workflow

1. Read product context -- Scan .chalk/docs/product/ for the product profile, PRDs with success metrics, JTBD docs, and any existing metrics definitions. Understand what the product does and who it serves before defining metrics.

2. Parse scope -- Extract from $ARGUMENTS the product area or business goal. If unspecified, build a company-level metrics framework using the product profile.

3. Determine the next file number -- Read filenames in .chalk/docs/product/ to find the highest numbered file. The next number is highest + 1.

4. Define the North Star metric -- Identify the single metric that best captures the core value the product delivers to users. It must be: measurable, actionable by the team, a leading indicator of revenue, and reflective of user value (not just business extraction).

5. Map input metrics -- Identify 3-5 input metrics that drive the North Star. Use the AARRR framework as a lens: Acquisition (how users find you), Activation (first value moment), Retention (users come back), Revenue (users pay), Referral (users bring others). Not all stages need a metric -- pick the ones that matter most.

6. Apply the HEART framework -- For key user journeys, consider: Happiness (satisfaction), Engagement (usage depth), Adoption (new feature uptake), Retention (continued use), Task success (completion rate). Use this to fill gaps the AARRR lens missed.