Analytics Tracking Planner

This skill starts from the questions your team needs data to answer, then derives the events and properties required to answer them — not the other way around. You specify your product, the three to five decisions that depend on analytics data, and your stack (GA4, Mixpanel, Amplitude, or PostHog). The skill builds a complete tracking plan: a naming convention locked in before the first event ships, a property table with types and allowed values, anonymous-to-known identity stitching rules, funnel definitions, EU consent constraints, and governance rules that keep the schema clean past the first quarter of growth.

A realistic input looks like: a B2B SaaS checkout flow, questions about where trials drop off and which features correlate with conversion to paid, running on PostHog, team of four with one developer. The skill asks four scoping questions — context, goal, constraints, audience — then produces an implementation-ready plan your developer can build from directly, without a follow-up meeting to interpret it.

Sample output excerpt — Event table (partial): Event: checkout_step_completed | Trigger: user advances past a checkout stage | Properties: step_name (string, enum: plan_select | payment | confirm), plan_id (string), user_id (string), anonymous_id (string) | Owner: backend-eng | Question answered: Where do trials stall before activating a paid plan? | Consent tier: functional (required for product operation, GDPR-exempt with legitimate interest basis)