tracking-plan-discoverylisted

Walk any app hands-on and build or update a real product-analytics tracking plan from what you actually see. Use this whenever someone needs an event taxonomy, a tracking plan, a measurement plan, an analytics spec, an event dictionary, instrumentation for GA4 / Firebase / Amplitude / Mixpanel / Segment / PostHog, or wants to audit or extend tracking that already exists. Use it when the ask is "what should we track", "our analytics are broken", "we have no funnel data", "design the events for this feature", "map the user journeys", or "the dev team needs a spec". It drives an Android emulator, an iOS simulator, a browser or a Figma file, screenshots every surface, groups parameters into reusable attribute packs, grades every event by how strong the evidence for it actually is, and ships a phased, buildable Excel workbook with embedded screenshots. Works for any app in any industry. Reach for it even when the person only says "events" or "instrumentation" and has not used the words tracking plan.
riadchaban994-bot/discovery-os · ★ 0 · Data & Documents · score 72

Install: claude install-skill riadchaban994-bot/discovery-os

# Tracking plan discovery Most tracking plans are written from memory in a document, and they are wrong in ways nobody notices until the data arrives months later. This skill exists to produce one from evidence instead: open the app, walk every journey, screenshot every surface, and write the plan from what is actually there. The single idea that makes this work: **be honest about what you have seen.** A plan that says "I watched this fire" for some events and "I designed this, confirm it" for others is far more useful than one that speaks with uniform confidence and is quietly fictional in half its rows. ## What you produce A multi-tab Excel workbook, built by `scripts/build_workbook.py` from a single JSON file. Sections you do not supply are simply skipped, so the same script serves a six-event first pass and a mature plan: | Tab | What it is | |---|---| | Read me | Architecture, conventions, identity, privacy, platform limits, rollout | | **Phase 1 build ask** | **The deliverable.** Only the events to build now, with source, evidence, screens, work estimate, parameters | | Roadmap | Phase 2 and 3, what earns each, and what was cut with the reason | | Attribute packs | Every parameter: required/conditional/optional, type, values, notes | | All events | The full target state, phased and evidence-graded | | User properties | Persistent attributes and their update rules | | Custom definitions | What to register in the analytics tool before shipping | | Key events & audien