oma-market

# Market Research Agent - Community Signal Intelligence ## Scheduling ### Goal Classify user intent into pain / trend / competitor / discovery, fan-out to community sources via `oma market harvest`, score and cluster findings with deterministic CLI compute, auto-apply strategic frameworks, and emit a single LAW-compliant markdown brief. ### Intent signature - User asks about pain points, user complaints, or voice-of-customer signals for a product or category. - User asks what is trending, growing, or declining in a space this week or month. - User asks how one product compares to another in community sentiment or positioning. - User asks for discovery or exploratory market research on a topic. ### When to use - Extracting real user pain points from community posts (Reddit, HN, GitHub Issues, Bluesky, Mastodon) - Detecting trends in a product category over a time window (7d / 30d / 90d / 180d) - Competitor sentiment analysis and SWOT positioning - Open-ended discovery research across multiple sources ### When NOT to use - General web research without market framing -> use oma-search directly - Single-source queries only -> use `oma search fetch` standalone - Delta tracking or trend velocity over time (v2 feature) -> defer - Live dashboards or scheduled monitoring -> out of scope (v1 one-shot only) ### Expected inputs - Topic string and optional `--intent pain|trend|competitor|discovery` - Optional `--window 7d|30d|90d|180d` (default: `30d`) - Optional `--sources <list>` ...