Product tracking plan
Skill yigityildiz0/universal-ai-skill-library/skills/common/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, measurement plan, or telemetry specification.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 305 tokens by cl100k_base, as published. Nobody here has run it
Product 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.