Lumen Recon

---
name: lumen-recon
description: Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Analytics Reconnaissance

You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics.

## Steps

### Step 0: Detect Environment

Scan for analytics and tracking indicators:

```bash
# Analytics libraries
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5
find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -5

# Tracking calls
find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" 2>/dev/null | xargs grep -l "track\|identify\|capture\|logEvent\|analytics\." 2>/dev/null | head -20

# Analytics docs
find . -name "*.md" | xargs grep -l "metrics\|funnel\|retention\|event\|dashboard\|OKR\|north star" 2>/dev/null | head -10
```

### Step 1: Inventory Analytics Stack

Identify:

- **Analytics platform** — PostHog, Mixpanel, Amplitude, Segment, GA4, custom, or none
- **Backend tracking** — server-side events sent (Python/Node/Go SDKs)
- **Frontend tracking** — client-side events (JS/TS SDKs, autocapture)
- **Data warehouse** — BigQuery, Snowflake, Redshift, or none
- **BI tool** — Metabase, Looker, Grafana, Superset, or none

### Step 2: Inventory Events Being Tracked

Read tracking code and list:

| Event Name | Where Fired    | Properties | Notes      |
| ---------- | -------------- | ---------- | ---------- |
| [event]    | [page/service] | [props]    | [any gaps] |

Note: missing events for key user actions (sign up, activation, first value, churn signals).

### Step 3: Inventory Metric Definitions

Look for:

- **North Star metric** — single metric representing core value delivery
- **Input metrics** — leading indicators driving North Star
- **OKR key results** — specific, measurable targets for this period
- **Dashboard definitions** — what's on main product dashboard

Flag metrics defined but not instrumented, or instrumented but not displayed.

### Step 4: Assess Analytics Health

| Dimension                  | Status  | Note |
| -------------------------- | ------- | ---- |
| North Star defined         | [✓/✗/~] |      |
| Activation event tracked   | [✓/✗/~] |      |
| Retention tracked (D7/D30) | [✓/✗/~] |      |
| Funnel steps instrumented  | [✓/✗/~] |      |
| User identity stitched     | [✓/✗/~] |      |
| Revenue events tracked     | [✓/✗/~] |      |

### Step 5: Present Assessment

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

```
## Analytics Reconnaissance

**Platform:** [tool] | **Backend tracking:** [✓/✗] | **Frontend tracking:** [✓/✗]
**Total events tracked:** [N or unknown] | **North Star:** [metric or UNDEFINED]

### Events Inventory
| Lifecycle Stage | Events | Gap |
|----------------|--------|-----|
| Acquisition    | [N]    | [gap or none] |
| Activation     | [N]    | [gap or none] |
| Retention      | [N]    | [gap or none] |
| Revenue        | [N]    | [gap or none] |
| Referral       | [N]    | [gap or none] |

### Metric Definitions
- **Defined and tracked:** [list]
- **Defined but not tracked:** [list]
- **Not defined:** [key metrics that should exist]

### Critical Gaps
- [RED] [missing event that blocks product understanding]
- [YELLOW] [incomplete tracking or inconsistent naming]

### Recommended Next Step
[Which instrumentation gap to close first]
```

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.