event-tracking-plan
Skill3 starsChanged 8 months agoMITView on GitHub
Create or audit an event tracking plan for product, growth, and analytics workflows. Use when a team needs a source-of-truth taxonomy, instrumentation plan, and data governance rules.
In this repository19 other files it gives its agents.
- customer-discovery-jtbd-synthesisSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill to design, repair, or review a product analytics tracking plan.
- Distinctive: line 41
If these are missing, infer a reasonable first pass and label assumptions.
- Distinctive: line 45
Treat the tracking plan as the source of truth.
- Distinctive: line 46
Prefer human-readable event names.
- Distinctive: line 47
Use an object-action naming convention unless the repo already uses a different standard.
- Distinctive: line 198
When auditing an existing taxonomy, explicitly call out:
- Distinctive: line 208
If the product is B2B SaaS, strongly prefer including org/account properties and account-level events where relevant.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Event Tracking Plan
Use this skill to design, repair, or review a product analytics tracking plan.
What this skill must produce
Always produce:
- Tracking objective
- Critical event
- North Star tie-in
- Core funnel
- Event taxonomy
- Property taxonomy
- Identity model
- Client vs server instrumentation map
- Data quality / governance checks
- Implementation backlog
Inputs to gather
If available, extract:
- Product name
- Core user journey
- Target conversion / activation event
- Existing event names
- Current analytics stack
- User/account model
- Main reporting questions
- Planned experiments / funnels
- Regions / privacy constraints
- Existing dashboards / warehouse / CDP
If these are missing, infer a reasonable first pass and label assumptions.
Working rules
- Treat the tracking plan as the source of truth.
- Prefer human-readable event names.
- Use an object-action naming convention unless the repo already uses a different standard.
- Include event purpose, owner, source, and destination.
- Track only data that is necessary and useful.
- Distinguish clearly between event properties, user properties, and organization properties.
- Explicitly mark whether each event is client-side or server-side.
- Design for analysis and activation.
Step-by-step method
Step 1: define the business questions
List the 5-10 most important questions the team wants the data to answer.
Examples:
- What drives activation?
- Where do users drop in onboarding?
- Which behaviors correlate with retention?
- What qualifies an account as product-qualified?
- Which experiments require new events?
Step 2: define the critical event
Choose the user action that most closely represents the core value exchange in the product.
State:
- why this is the critical event
- what should count as an active user
- what should not count as active usage
Step 3: map the core funnel
Define the critical path funnel from first touch to activation / conversion.
For each stage specify:
- stage name
- target event
- key failure mode
- key diagnostic event
Step 4: design the event taxonomy
For every required event include:
- canonical event name
- plain-English purpose
- when it fires
- trigger source
- actor
- destinations
- owner
Step 5: design properties
For each event list required properties with:
- property name
- type
- example value
- why it is needed
- whether required or optional
Then separately list:
- user properties
- org/account properties
Step 6: define instrumentation ownership
For each event specify whether it is:
- client-side
- server-side
- both
- derived / warehouse modeled
Step 7: define governance rules
Specify:
- naming rules
- deprecation rules
- duplicate event checks
- required documentation fields
- QA checklist
- audit cadence
Step 8: create implementation order
Prioritize events into:
- P0 must-have
- P1 next
- P2 later
Required outputs
Tracking objective
Summarize the job of this tracking plan in 2-4 sentences.
Critical event
- Event:
- Why it matters:
- Active user definition:
- Non-active noise to exclude:
North Star tie-in
Explain how the critical event and funnel relate to the team’s North Star or primary KPI.
Core funnel
| Stage | Target event | Why it matters | Common drop-off cause |
Event taxonomy
| Event name | Purpose | Fires when | Source | Owner | Priority |
Event properties
| Event | Property | Type | Example | Required? | Why needed |
User properties
| Property | Type | Example | Why needed |
Account / org properties
| Property | Type | Example | Why needed |
Identity model
State clearly:
- anonymous ID
- user ID
- account / org ID
- merge behavior
- multi-org behavior
- device/session considerations
Client vs server instrumentation map
| Event | Client | Server | Notes |
Data quality / governance checks
- Naming convention:
- Required docs:
- QA process:
- Audit cadence:
- Deprecation process:
- PII guidance:
- Common failure patterns to watch:
Implementation backlog
| Priority | Task | Owner | Why now |
Additional rules
When auditing an existing taxonomy, explicitly call out:
- duplicates
- ambiguous names
- events without business purpose
- missing properties
- events that cannot support the desired funnels or experiments
- active-user definitions that are too shallow
- places where account-level context is missing
If the product is B2B SaaS, strongly prefer including org/account properties and account-level events where relevant.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

