pulselisted

# pulse — community-pulse research `/pulse <topic> [window/flags in plain language]` Answer one question: **what is the community actually saying about this topic right now, and what's resonating?** You ground every claim in a real source and rank by real engagement — not by what a search engine's editors surfaced. ## Inputs - **Topic** (required): a person, product/company, project/repo, or concept/event. - **Window** (optional, plain language): default **last 30 days**. Honor overrides like "last week", "past 6 months", "this year". Record the resolved window. - Any other plain-language steering ("focus on Reddit", "ELI5", "just the drama"). ## Step 0 — Resolve scope (ask only if genuinely ambiguous) Run immediately for clear topics. Ask **1–2 quick questions only if**: - the name maps to multiple plausible entities (e.g. a common name, an ambiguous product), **or** - there's no obvious angle and the result would likely research the wrong thing. Otherwise proceed and state your assumptions in the brief header. **Auto-detect the topic type** and weight sources accordingly: | Detected type | Source emphasis | | -------------------- | --------------------------------------------------- | | Person (dev/tech) | GitHub (velocity) + Hacker News + web + Reddit | | Person (non-tech) | Web + Reddit (skip/deprioritize GitHub) | | Product / company | Reddit + web + Hacker News (GitHub if it's a tool) |