competitive-intelligence-monitor
Competitive Intelligence Monitor Skill
Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
Required Inputs
Ask the user for these if not provided:
- Competitors to monitor (list of company names)
- Your current roadmap or strategic priorities (to assess relevance of signals)
- Previous brief or last run summary (for diff mode — what's new vs. last time)
- Time period (this week, this month)
Signal Categories to Monitor
- Product signals: New features, removals, UX changes, beta programmes
- Pricing signals: Changes to tiers, free limits, enterprise terms
- Hiring signals: Job postings revealing strategic bets
- Partnership signals: Integrations, acquisitions, ecosystem moves
- Messaging signals: Changes in positioning, audience, value proposition
Process
First Run (Full Report)
- For each competitor provided, scan all five signal categories
- Categorise each signal found
- Assess: reactive (responding to market) or proactive (setting direction)?
- Rate threat level: High / Medium / Low / Watch
- Connect each signal to a specific item on the provided roadmap
- Recommend response: Accelerate / Deprioritise / Monitor / Investigate
- Validate — Every High signal must have a specific recommended action and owner. "Monitor" is only acceptable for Low and Watch ratings.
Subsequent Runs (Diff Only)
- Compare current signals against previous run summary
- Output ONLY what is new or changed since last run
- Flag if a previously Low signal has escalated to High
- Keep output under 300 words — brevity is the point
Output Structure
Competitive Intelligence Brief — [Date]
New Since Last Run: [n signals]
🔴 High Priority
[Competitor]: [Signal] → [Implication] → [Recommended action + owner]
🟡 Watch
[Competitor]: [Signal] → [Why it matters now]
✅ No Change
[Competitors with no new signals this week]
This Week's Strategic Summary: [2 sentences max — what is the overall competitive landscape doing?]
Quality Checks
- Every High-priority signal has a specific response action and owner
- Signals are categorised (not just listed as "they did X")
- Roadmap connections are specific (not "generally relevant")
- Diff mode output is under 300 words
- Strategic summary describes the landscape trend, not just repeats individual signals
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17executive-summary
Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
15