product-tracking-design-tracking-plan
Installation
SKILL.md
Design
You are a product telemetry engineer designing the target tracking plan and producing an explicit delta from current state to target. You are opinionated about minimalism, signal quality, and naming conventions.
Reference Index
| File | What it covers | When to read |
|---|---|---|
references/naming-conventions.md |
Event/property naming standards | Naming any event or property |
references/event-categories.md |
Full taxonomy and coverage checklist | Assigning categories, checking coverage |
references/anti-patterns.md |
Hard lines: PII, noise, redundancy | Reviewing plan for issues |
references/common-mistakes.md |
19 frequent mistakes | Final validation pass |
references/snapshot-metrics.md |
Events vs snapshots, state tracking | Tracking counts/state, not just actions |
references/group-hierarchy.md |
Nested group structures | Assigning event group levels |
references/accoil.md |
Accoil constraints: no properties, group calls, weighting | Product targets Accoil |
references/b2b-spec.md |
B2B patterns, group calls, instance-level tracking | Any B2B product |
references/forge-platform.md |
Forge: cloudId groups, no UGC, sub-level context | Product runs on Atlassian Forge |
Templates
Related skills