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

  1. List the decisions, metric definitions, hypotheses, and journeys the instrumentation must support.
  2. Map the observable states and value events from eligibility through exposure, action, outcome, failure, and recovery.
  3. Reuse the existing taxonomy where semantics match. Define each new event with trigger, actor, object, timestamp, source, environment, and exclusions.
  4. Define required properties, types, allowed values, null behavior, cardinality, and versioning. Keep mutable context distinct from event facts.
  5. Specify anonymous, user, account, device, and session identity rules, including merges, cross-device behavior, bots, internal users, and consent boundaries.
  6. Map events to metrics and analyses. Identify joins, attribution windows, late data, duplication, ordering, and warehouse or client differences.
  7. Create implementation ownership and a validation plan using fixtures, expected payloads, schema checks, volume checks, and end-to-end environment evidence.
  8. Define monitoring, documentation, deprecation, and change control so semantic drift becomes visible.

BuildBetter Acceleration

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026