# Competitive Response Monitor

> This skill monitors competitor moves and assesses whether they require a strategic product response, filtering signal from noise in the competitive landscape. Use when a competitor ships a major feature, announces a pricing change, or enters an adjacent market. Also consider when sales reports increasing competitive displacement in deal cycles. Suggest when the team has not performed a competitive review in over a quarter and market dynamics may have shifted.

- Skill: `mittuled/competitive-response-monitor` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add mittuled/competitive-response-monitor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mittuled/competitive-response-monitor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mittuled (https://skillmd.com/u/mittuled)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mittuled/competitive-response-monitor

---


# competitive-response-monitor

## Agent: VP Product
L1 product leader responsible for opportunity framing, MVP definition, PRD assembly, go-live coordination, and post-launch monitoring. Owns the product strategy and roadmap from idea through GA.

Department ethos: [ideal-product.md](../../../../departments/product/ideal-product.md)

## Skill Description
Monitors competitor moves and assesses whether they require a strategic product response, separating meaningful threats from market noise.

## When to Use
- When a direct competitor launches a feature that overlaps with your product's core value proposition
- When sales surfaces a pattern of lost deals citing a specific competitor capability
- When a competitor announces a pricing or packaging change that could shift buyer expectations
- When a new entrant appears in your category or an adjacent player expands into your space

## Workflow
1. **Capture the signal**: Document the competitor move with specifics -- what shipped, pricing change, partnership announced, or market entered. Include source, date, and confidence level. Deliverable: competitive signal brief.
2. **Assess customer impact**: Evaluate whether the move affects your ICP segments. Check if existing customers are asking about the competitor capability and whether prospects are citing it in evaluations. Deliverable: customer impact assessment with segment-level exposure rating.
3. **Gauge strategic severity**: Rate the threat on two axes -- impact on your differentiation and urgency of response. Classify as ignore, monitor, respond-at-pace, or respond-urgently. Deliverable: severity classification with rationale.
4. **Evaluate response options**: For moves classified as respond-at-pace or higher, outline possible responses: accelerate an existing roadmap item, build a counter-feature, adjust positioning, update pricing, or strengthen an adjacent moat. Deliverable: response options matrix with effort, timeline, and expected impact.
5. **Recommend and escalate**: Select the recommended response, document trade-offs, and escalate to leadership if the response requires roadmap reprioritization or budget. Deliverable: recommendation memo with decision request.
6. **Update competitive intelligence**: Add findings to the competitive landscape tracker for ongoing reference by sales, marketing, and product teams. Deliverable: updated competitive tracker entry.

## Anti-Patterns
- **Reactive feature matching**: Copying every competitor feature without evaluating strategic fit. *Why*: Feature-chasing fragments the roadmap, dilutes differentiation, and burns engineering cycles on capabilities that may not matter to your ICP.
- **Ignoring displacement signals**: Dismissing sales feedback about competitive losses as anecdotal. *Why*: Pattern blindness lets a competitor erode market share incrementally until the damage is systemic and expensive to reverse.
- **Panic-driven reprioritization**: Immediately halting current work to respond to every competitor announcement. *Why*: Constant context-switching destroys sprint velocity, demoralizes engineering, and produces half-finished responses that ship late.
- **Stale competitive data**: Relying on a competitive analysis from six months ago without refreshing. *Why*: Markets move fast; outdated intelligence leads to positioning that fails in live deal cycles.

## Output
**On success**: A severity-classified competitive signal brief with a recommended response (or explicit decision to not respond), updated competitive tracker, and escalation to leadership if roadmap changes are required.
**On failure**: Report which data sources were unavailable (e.g., no win/loss data for the quarter, no customer feedback on the competitor feature), what assumptions were made, and recommend specific data collection actions before a response decision can be finalized.

## Related Skills
- [`assumption-mapper`](../assumption-mapper/SKILL.md) — sibling skill under the same agent — combine with assumption-mapper for end-to-end coverage
- [`business-model-sketcher`](../business-model-sketcher/SKILL.md) — sibling skill under the same agent — combine with business-model-sketcher for end-to-end coverage
- [`goal-framer`](../goal-framer/SKILL.md) — sibling skill under the same agent — combine with goal-framer for end-to-end coverage
- [`prd-assembler`](../prd-assembler/SKILL.md) — sibling skill under the same agent — combine with prd-assembler for end-to-end coverage
- [`design-partner-programme-builder`](../design-partner-programme-builder/SKILL.md) — sibling skill under the same agent — combine with design-partner-programme-builder for end-to-end coverage
- [`gate-12-evaluator`](../gate-12-evaluator/SKILL.md) — sibling skill under the same agent — combine with gate-12-evaluator for end-to-end coverage
- [`idea-critic`](../idea-critic/SKILL.md) — sibling skill under the same agent — combine with idea-critic for end-to-end coverage
- [`launch-coordinator`](../launch-coordinator/SKILL.md) — sibling skill under the same agent — combine with launch-coordinator for end-to-end coverage
- [`moat-analyzer`](../moat-analyzer/SKILL.md) — sibling skill under the same agent — combine with moat-analyzer for end-to-end coverage
- [`mvp-definer`](../mvp-definer/SKILL.md) — sibling skill under the same agent — combine with mvp-definer for end-to-end coverage
- [`north-star-metric-reviewer`](../north-star-metric-reviewer/SKILL.md) — sibling skill under the same agent — combine with north-star-metric-reviewer for end-to-end coverage
- [`opportunity-framer`](../opportunity-framer/SKILL.md) — sibling skill under the same agent — combine with opportunity-framer for end-to-end coverage
- [`packaging-designer`](../packaging-designer/SKILL.md) — sibling skill under the same agent — combine with packaging-designer for end-to-end coverage
- [`pitch-narrator`](../pitch-narrator/SKILL.md) — sibling skill under the same agent — combine with pitch-narrator for end-to-end coverage
- [`pricing-v1-setter`](../pricing-v1-setter/SKILL.md) — sibling skill under the same agent — combine with pricing-v1-setter for end-to-end coverage
- [`product-feedback-ingestion`](../product-feedback-ingestion/SKILL.md) — sibling skill under the same agent — combine with product-feedback-ingestion for end-to-end coverage
- [`sla-definer`](../sla-definer/SKILL.md) — sibling skill under the same agent — combine with sla-definer for end-to-end coverage