internal-signal-scoutinglisted

# Internal Signal Scouting ## Why this exists Good product ideas don't only come from customers — they come from the sales rep who hears the same objection every week, the support agent who's answered the same workaround forty times, the CS manager who sees a churn pattern before it shows up in the dashboard. That knowledge usually just scrolls by in Slack and is gone. This skill turns it into the same kind of structured, accumulating signal as customer-facing feedback — using the same taxonomy as `call-insight-extraction` and `feedback-triage-scoring`, so everything can eventually merge into one prioritized view. ## Scope and trust, before anything else This is the one part of this skill that matters more than the extraction method: **only monitor channels that are explicitly designated for this purpose** (e.g., a channel literally named `#product-ideas` or `#support-escalations` that the team knows is being read this way). Do not run this against general team channels, DMs, or anything not opted into being scouted. Two reasons, not one: - **Trust** — people self-censor or stop posting candidly the moment a channel feels surveilled rather than opted-in. - **Precision** — a blanket sweep of every channel returns mostly noise; a scoped sweep of channels people already use to flag things returns mostly signal. If you're not sure a channel is fair game, it isn't — ask first. ## Process ### 1. Sweep the designated channels on a fixed cadence Weekly is usually right for a