# Pestel Delta Monitor

Quarterly re-scan of a prior PESTEL analysis.

- 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 pestel-delta-monitor -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new, turning PESTEL from a workshop artifact into a radar.

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

# PESTEL Delta Monitor

## Purpose

Refresh a PESTEL analysis by diffing each factor, Political, Economic, Social, Technological,
Environmental, Legal, against the prior run and reporting **material movement only**: **search plan
→ factor-by-factor diff → broken assumptions → new entrants to the frame → next-step options.** Macro
factors move slowly, which is exactly why teams stop looking; the value of a cadence is catching the
two factors that moved, not re-debating the twenty that didn't. Diffing also reveals which baseline
entries were live assumptions versus furniture, **broken assumptions are the real output.**

## Input

**Works best with:** the prior PESTEL analysis (pasted or attached) and the product/market scope it
covered, this skill *requires* a baseline to diff against.
**Also useful:** any events since the last run you already suspect matter, they get checked first.

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?** This is the one investigation skill with a hard prerequisite: with no
baseline, it recommends running [`pestel-analysis`](../pestel-analysis/SKILL.md) first and stops, there is nothing to diff. (That referral *is* the empty-handed path: you leave knowing exactly what
to do first.)

**Example invocation:** `PESTEL delta against the attached Q1 analysis, scope is our EU payments
product; I suspect the new AI liability directive matters.`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/pestel-delta-monitor/SKILL.md