docs-funnel-mapperlisted

# docs-funnel-mapper — Find where users fall out The classic funnel question, applied to docs: "60% land on `/quick-start`, 40% reach `/billing`, but only 5% click `Upgrade`. Where did the other 35% go and why?" This skill runs over real session data — the ordered page-to-page paths readers actually walked — clusters the recurring multi-step paths, and flags the high-volume / low-completion ones as `conversion_problem` findings. ## When to run - Bi-weekly. - After any navigation / sidebar change. - Before pricing or onboarding rewrites — establishes baseline. ## Workflow Standard four-stage docs-insights pipeline. Slice = `funnel`. See [`docs-utm-analyzer`](../docs-utm-analyzer/SKILL.md) for the canonical step-by-step. - **Collector:** the top recurring 3-step reader paths through the docs, plus per-page traffic totals to attach volume to each step. Any session-level signal that shows what a reader did next belongs here. - **Clusterer:** groups by `journey_pattern`, computes `completion_rate` = % of sessions reaching at least one conversion page (defined as pages containing CTA `Upgrade`, `Sign up`, `Book demo`, or pages matching the workspace's billing/pricing slug). - **Reporter:** `conversion_problem` for completion_rate < 0.2; `broken_journey` when a doc-graph-implied transition is missing from real journeys. ## What this skill catches | Pattern | Example finding | |---|---| | **Drop on billing page** | `quick-start → features → billing` has 4k sessions, but only