product-tracking-plan
Design a privacy-aware product telemetry plan with event taxonomy, properties, identity rules, validation, and decision links. Use when asked what to track, to create an analytics plan, event schema,
SKILL.mdskills/common/product-tracking-plan/SKILL.md
GitHubProduct Tracking: Design a Plan
Turn product decisions into a minimum useful telemetry contract. Prefer a small, well-defined event set over exhaustive click logging.
Inputs
Read product-tracking-model and product-tracking-audit artifacts when available. If not, state which decisions remain assumptions.
Workflow
- Start from decision questions, success measures, and core value moments.
- Define events as stable past-tense business actions, not UI implementation details.
- For each event, specify trigger, required properties, optional properties, actor/context, destination boundary, and validation case.
- Define identity, account/group, anonymous-to-known, consent, opt-out, deletion, retention, and internal/test-user handling without assuming provider APIs.
- Add a test matrix for happy path, duplicate delivery, retry, offline/error, and prohibited-data cases.
- Compare with the audit and label additions, renames, deprecations, and unresolved decisions.
Deliverable
Produce a reviewable plan, optionally at .telemetry/tracking-plan.md:
Objective and decisions
Event taxonomy
Event contract table
Identity and privacy contract
Measurement definitions and caveats
Implementation sequence
Validation and rollout plan
Delta from current state
Guardrails
- Do not include secrets, unrestricted text, sensitive categories, or unnecessary identifiers.
- Do not silently choose a vendor or invoke external APIs.
- Require a reviewed plan before
product-tracking-implementationchanges code.