competitor-signal-tracker
Competitor Signal Tracker Skill
Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
Required Inputs
Ask the user for these if not provided:
- Competitor name(s) and the signals/updates to analyse
- Your product's current roadmap or strategic priorities (to assess relevance)
- Time period the signals cover (this week, this month, etc.)
Signal Categories to Track
- Product signals: New features, removals, UX changes, beta programmes
- Pricing signals: Changes to tiers, free limits, enterprise terms
- Hiring signals: Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment)
- Partnership signals: Integrations, acquisitions, ecosystem moves
- Messaging signals: Changes in positioning, target audience, value proposition
Process
- For each competitor update provided, categorise the signal type
- Assess: Is this reactive (responding to market) or proactive (setting direction)?
- Rate strategic threat level: High / Medium / Low / Watch
- Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
- Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
- Validate — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats.
Output Structure
Competitive Intelligence Report — [Date]
[Competitor Name]
Signal: [What they did] Signal Type: [Product / Pricing / Hiring / Partnership / Messaging] Reactive or Proactive: [assessment] Threat Level: [High / Medium / Low / Watch] Implication for Us: [Specific connection to our roadmap or strategy] Recommended Response: [Action + owner + timeline]
Strategic Summary
[2-3 sentences on the overall competitive landscape shift this period]
Quality Checks
- Every signal is categorised (not just described)
- Threat level is justified — not assigned arbitrarily
- High-threat signals have specific recommended responses (not "monitor")
- Implications connect to specific roadmap items or strategic bets
- Strategic summary gives a landscape-level view, not just a list of 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