solo-metrics-track

# /metrics-track

Set up a metrics tracking plan for a project. Defines PostHog event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds based on lean startup principles.

## MCP Tools (use if available)

- `kb_search(query)` — find PostHog methodology, analytics patterns

If MCP tools are not available, fall back to Grep + Read.

## Methodology Reference

This skill implements metrics tracking based on lean startup principles:
- **Relative metrics vs niche benchmarks** — compare against your own trajectory, not vanity averages
- **Kill/iterate/scale decision rules** — data-driven thresholds for product decisions (see step 7 below)

## Steps

1. **Parse project** from `$ARGUMENTS`.
   - Read PRD for features, ICP, monetization model.
   - Read CLAUDE.md for stack (iOS/Web/both).
   - If empty: ask via AskUserQuestion.

2. **Detect platform:**
   - iOS app → PostHog iOS SDK events
   - Web app → PostHog JS SDK events
   - Both → cross-platform identity (shared user ID across platforms)

3. **Load PostHog methodology:**
   - If MCP available: `kb_search("PostHog analytics events funnel identity")`
   - Otherwise: check project docs for existing analytics configuration
   - Extract: event naming conventions, identity resolution, funnel pattern

4. **Define event funnel** based on PRD features:

   Standard funnel stages (adapt per product):
   ```
   Awareness → Acquisition → Activation → Revenue → Retention → Referral
   ```

   Map to concrete events:

   | Stage | Event Name | Trigger | Properties |
   |-------|-----------|---------|------------|
   | Awareness | `page_viewed` | Landing page visit | `source`, `utm_*` |
   | Acquisition | `app_installed` or `signed_up` | First install/signup | `platform`, `source` |
   | Activation | `core_action_completed` | First key action | `feature`, `duration_ms` |
   | Revenue | `purchase_completed` | First payment | `plan`, `amount`, `currency` |
   | Retention | `session_started` | Return visit (D1/D7/D30) |...