Use this skill to convert product analytics instrumentation, event taxonomy, identity, funnel, privacy, QA, and metric-owner questions into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify decisions to support, user journey, platforms, event sources, identity model, consent/privacy constraints, downstream metrics, dashboards, experiments, and current data-quality failures.
- Read
references/product-analytics-instrumentation-patterns.md. - Classify tracking as client event, server event, billing/support join, experiment exposure, attribution touch, lifecycle event, error state, or derived metric input.
- Define event contract, property schema, identity rules, consent gating, QA plan, dashboard owner, release gate, and drift monitoring.
- Produce instrumentation plan, state machine, decision table, event schema, QA checklist, and rollout plan.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not instrument everything; track decision-relevant events with clear owners and retention/privacy constraints.
- Do not use client-only analytics for billing, compliance, entitlement, or critical operational truth.
- Do not ship events without property schema, identity behavior, consent handling, and QA fixtures.
- Do not let dashboards define metrics independently from the event/metrics source of truth.
Output format
Analytics context:
Audience / source of truth / risk boundary:
Instrumentation plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Event contracts, QA, privacy, and dashboard handoff:
- <trigger> -> <policy, metric, edge case, support note>