measure-instrumentation-spec

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Instrumentation Spec
3 
4An instrumentation spec defines what analytics events to track, when to fire them, and what properties to include. It serves as a contract between product and engineering, ensuring consistent data collection that enables accurate measurement. Good instrumentation specs prevent the "we can't answer that question because we didn't track it" problem.
5 
6## When to Use
7 
8- Before engineering implements a new feature
9- When defining analytics requirements for experiments
10- When auditing existing tracking for gaps or inconsistencies
11- When onboarding a new analytics tool
12- Before launch to ensure measurement is in place
13 
14## When NOT to Use
15 
16- You are specifying the dashboard built on top of the events -> use `measure-dashboard-requirements`
17- You need experiment-specific metrics and variants, not product-wide tracking -> use `measure-experiment-design`
18- The feature itself is not yet specified (no flows to instrument) -> use `deliver-prd` first
19- You are analyzing data you already collect -> use `measure-experiment-results` or `measure-survey-analysis`
20 
21## Instructions
22 
23When asked to create an instrumentation spec, follow these steps:
24 
251. **Define Analytics Goals**
26   Start with the questions you need to answer. What will you measure? What decisions will this data inform? This prevents over-instrumentation while ensuring nothing important is missed.
27…