Product Tracking Skills

Reads your repository and builds a concrete tracking plan: it scans front-end and back-end code, finds UI interactions, API endpoints, and database writes, and maps them to events, properties, and user traits. You get a structured schema that lists event names, required and optional properties, data types, and where each event should fire in code. It uses seven slash commands to run targeted tasks and a background agent that watches for code changes and rescans incrementally.

Generates ready-to-install instrumentation: it spits out SDK wrapper code, helper functions, and example calls for over 25 analytics platforms including Segment, Amplitude, Mixpanel, and PostHog. It also creates type definitions and unit-test stubs so your devs can import tracking helpers, run tests, and avoid raw string event names scattered across files. You can pick platform-specific options or a neutral interface for multi-tool setups.

Reports gaps and duplicates: the tool flags missing properties, inconsistent naming, and events that look redundant across pages or services. It produces a changelog of what it added or updated and links findings back to source files and git commits so reviewers can approve instrumentation PRs alongside feature code.

Imagine a PM wanting weekly funnel numbers: instead of context-switching into analytics UIs and hunting for missing events, the team runs a slash command, reviews the generated schema and wrapper code, and merges instrumented changes with CI tests. That saves hours of back-and-forth and prevents shipping features without the right telemetry.