From pm-analytics
Define an analytics instrumentation plan — what to track, why, and how. Use before building a feature to ensure the right events are captured, or to audit an existing instrumentation setup.
How this command is triggered — by the user, by Claude, or both
Slash command
/pm-analytics:product-analytics [plan | audit] [feature or product area]The summary Claude sees in its command listing — used to decide when to auto-load this command
Produces an analytics instrumentation plan or audits existing tracking. Ensures you can answer the questions that matter post-launch. ## Routing - **`plan [feature]`**: design the instrumentation for a new feature. - **`audit [area]`**: review existing tracking and identify gaps. - **No argument**: ask questions below first. ## Questions (no argument) ## Output (plan) **Analytics Plan: [Feature Name]** **Questions this instrumentation answers** The specific product questions that drive the event design: 1. [Question] → answered by [event/property] 2. [Question] → answered by [event/...
Produces an analytics instrumentation plan or audits existing tracking. Ensures you can answer the questions that matter post-launch.
plan [feature]: design the instrumentation for a new feature.audit [area]: review existing tracking and identify gaps.Before I work on the instrumentation, a few questions:
1. Plan new instrumentation or audit existing?
2. What feature or product area?
3. What questions do you need to answer post-launch?
4. What analytics tool are you using? (Amplitude / Mixpanel / Segment / PostHog / custom)
5. What's already tracked? (helps avoid redundancy)
Answer as many as you can.
Analytics Plan: [Feature Name]
Questions this instrumentation answers The specific product questions that drive the event design:
Event taxonomy
| Event name | Trigger | Properties | Notes |
|---|---|---|---|
| [feature]_started | User begins the flow | user_id, plan, source | |
| [feature]_completed | Successful completion | user_id, duration, method | |
| [feature]_error | Error encountered | user_id, error_type, step | |
| [feature]_abandoned | Exit before completion | user_id, last_step |
User properties to update Properties on the user profile that this feature affects:
Funnel definition The conversion funnel for this feature: Step 1 → Step 2 → Step 3 → Completion
Implementation notes Where events fire (client / server / both), any sampling, PII handling.
Review existing events against the questions that need answering. Flag: missing events, redundant events, inconsistent naming, PII in properties, events that fire but connect to no dashboard or decision.
Instrument for questions, not for completeness. Tracking every click sounds thorough; it produces noise. Define the questions first, then design exactly the events needed to answer them.
npx claudepluginhub songd-85/pm-ops --plugin pm-analytics