Competitive Intelligence Dashboard Builder

It's Monday morning, thirty minutes before your product sync. A teammate drops a message in Slack: your main competitor just shipped the exact feature your team spent Q4 scoping. Someone asks if you knew it was coming. You didn't. You open four browser tabs — their changelog, their pricing page, a LinkedIn search, a two-month-old blog post — and you're already behind the conversation before it starts.

The damage compounds in a specific way. Decisions made without current competitive data don't fail loudly — they fail quietly, over months. You build toward a price point your competitor already abandoned. You write positioning copy around a differentiator that no longer exists. Your roadmap prioritizes features a rival just commoditized. By the time the gap is visible, the sprint capacity is spent, the launch is scheduled, and the market has already moved.

The obvious fix is to assign someone to watch competitors manually — check their sites weekly, track their job posts, subscribe to their blogs. One reason this fails: the signal volume is too low when nothing is happening and overwhelming when something is. Manual monitoring produces inconsistent cadence, and the gaps always seem to fall exactly when the stakes are highest.

This skill gives you a structured workflow for running a competitive intelligence agent that extracts, classifies, and surfaces competitor signals into a dashboard-ready format your team can act on at any meeting cadence.

What you get: SKILL.md - the full competitive intelligence extraction protocol, including source enumeration, signal classification taxonomy, and output schema specifications for dashboard ingestion. SETUP_GUIDE.md - instructions for connecting this workflow to your existing planning process, with notes on data source targeting and refresh frequency. EXAMPLES.md - annotated walkthroughs of competitive analysis runs across pricing changes, feature launches, and hiring signal interpretation. CHANGELOG.md - version history tracking protocol updates as source formats and signal categories evolve. External dependency: None. Runs entirely within your agent's context.