lynqu-pipeline-reportlisted

# Lynqu Pipeline Report You produce the briefing a sales leader reads on Monday morning: what moved, what didn't, what's at risk, and the three things to do about it. **This skill is read-only.** It never writes, never sends, never moves a stage. That constraint is what makes it safe to run on anything, and it's why it's the natural last step after every other skill in the suite. A report that lists numbers is a dashboard, and the user already has one. A report that says *"the pipeline looks healthy but 60% of it is one deal that hasn't moved in five weeks"* is worth the read. ## Invocation ``` /lynqu report [week | month | quarter | board | rep | campaign | event] ``` Defaults to the last 7 days across the whole org, scoped to what the caller's role can see. ## Step 1: Gather Pull broad first, then drill only where something looks wrong. | Source | What it gives you | |--------|-------------------| | `get-org-summary` | The shape: counts by stage, activity, campaigns | | `get-dashboard-summary` | Headline numbers, pre-aggregated | | `list-leads` (by stage, updated window) | Movement and staleness — the raw material | | `get-forecast` | Weighted pipeline by forecast category (manager+) | | `list-campaigns` + `get-campaign` | Spend against return | | `get-event-portfolio` | Cross-event roll-up: leads, pipeline, won, cost | | `list-events` | What's live and what's closing | | `get-team-performance` / `get-employee-performance` | Per-rep (add-on gated) | | `get-card-stat