competitor-launch-radar

> **${var}** — Optional. `dry-run` skips notify (state still updates and article still writes). Empty = normal run. Today is ${today}. `ai-framework-watch` tracks momentum across a known 9-framework cohort (aeon anchor + langgraph/crewai/autogen/llamaindex/mastra/smolagents/dspy/pydantic-ai). That cohort is intentionally curated — but in 2026 a brand-new agent framework can post to Product Hunt, get 400 upvotes, hit the HN front page, and accumulate users before earning a single GitHub star. This skill is the radar for that blind spot: weekly Monday scan of Product Hunt RSS + HN Algolia for **new entrants** matching agent-framework keywords, filtered against the existing cohort and an LRU dedup state so each launch fires exactly once. Read `memory/MEMORY.md` for context. Read the last 8 days of `memory/logs/` to dedupe entrants already featured this week. Read `soul/SOUL.md` + `soul/STYLE.md` if populated to match voice. ## Why this exists `ai-framework-watch` answers "what did the known cohort ship this week?" — momentum, releases, breaking changes. It cannot answer "did a new framework just launch?" because the watchlist is hardcoded by design (drift erodes week-over-week comparability). Without a second skill watching the public-launch surfaces, the operator only learns about a new entrant when it crosses into their Twitter feed weeks later. By that point the framework already has stars, integrations, and momentum the operator could have engaged earlier. This skill cl...