# Competitive Intel Watch

Scheduled delta monitoring against a prior competitive snapshot.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-intel-watch -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-intel-watch -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-intel-watch -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-intel-watch -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Competitive Intel Watch

## Purpose

Monitor a competitive landscape for **material shifts** since the last run. Diff the world against the
previous snapshot; report only what changed, with evidence; flag which downstream artifacts need
updating. This is the skill that turns competitive research from a document into a cadence, the
weekly SIGINT sweep and monthly OSINT digest from the fusion cadence live here. A watch reports
*change*, not *state*: regenerating the same report weekly is theater, and "no material shifts this
cycle" is a valid, useful result.

## Input

**Works best with:** the previous Competitive Research Snapshot (pasted or attached), the baseline
this run diffs against, and the competitor list (defaults to those in the snapshot).
**Also useful:** anything specific you're watching for this cycle, and a materiality bar adjustment if
the default needs tightening or loosening.

Input supplied inline with the invocation, text after the skill name, a pasted context dump, or an
appended `ARGUMENTS:` line, counts as answers already given. Use it against the question budget;
don't re-ask.

**Arriving empty-handed? That works too.** With no prior snapshot, the skill falls back to **baseline
mode**: it produces a first snapshot using the `competitive-research-snapshot` structure and stops, the delta value starts on run two.

**Example invocation:** `Competitive intel watch, prior snapshot pasted below; this cycle I'm
specifically watching for pricing moves. [snapshot]`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/competitive-intel-watch/SKILL.md