What problem does it solve? Operators often cannot tell whether revenue numbers, pricing claims, and team billing behavior reflect reality or just marketing copy. This Skill separates revenue facts from customer incidents and code-backed product truth so billing decisions rest on evidence. ## Core Features & Use Cases - Revenue Snapshot: Normalize paid sales, active subscriptions, failed checkouts, refunds, disputes, and duplicate subscriptions with explicit live-data or snapshot timestamps. - Code-Backed Billing Truth: Inspect checkout, pricing page, entitlement calculation, and seat or quota handling to verify whether per-seat or team billing actually exists in code. - Decision Output: Produce a structured report covering snapshot, customer impact, product truth, decision, and product gap. - Use Case: A user asks whether duplicate Stripe charges mean duplicate value and whether per-seat billing is real. The Skill classifies the customer incident, inspects the entitlement code path, and ends with a refund-or-convert decision plus a backlog gap. ## Quick Start Analyze our recent Stripe sales and refunds, then verify in the codebase whether team per-seat billing is actually enforced and report the product gap.
