plan-product-instrumentation
Installation
SKILL.md
Plan Product Instrumentation
Contract
Instrumentation is a measurement contract, not an event inventory. Collect only data tied to a decision, define semantics before implementation, and minimize personal or sensitive data.
Workflow
- List the decisions, metric definitions, hypotheses, and journeys the instrumentation must support.
- Map the observable states and value events from eligibility through exposure, action, outcome, failure, and recovery.
- Reuse the existing taxonomy where semantics match. Define each new event with trigger, actor, object, timestamp, source, environment, and exclusions.
- Define required properties, types, allowed values, null behavior, cardinality, and versioning. Keep mutable context distinct from event facts.
- Specify anonymous, user, account, device, and session identity rules, including merges, cross-device behavior, bots, internal users, and consent boundaries.
- Map events to metrics and analyses. Identify joins, attribution windows, late data, duplication, ordering, and warehouse or client differences.
- Create implementation ownership and a validation plan using fixtures, expected payloads, schema checks, volume checks, and end-to-end environment evidence.
- Define monitoring, documentation, deprecation, and change control so semantic drift becomes visible.