pestel-delta-monitor

Diffs a prior PESTEL analysis against current macro factors to report material movement and broken assumptions.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill pestel-delta-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pestel-delta-monitor
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pestel-delta-monitor
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill pestel-delta-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PESTEL analyses typically become stale workshop artifacts that teams never revisit, leaving strategies silently dependent on outdated macro assumptions. This Skill turns PESTEL into a living radar by re-scanning a prior analysis on a quarterly cadence and reporting only what materially moved.

Core Features & Use Cases

  • Factor-by-Factor Diffing: Compares each Political, Economic, Social, Technological, Environmental, and Legal factor against the prior baseline, reporting movement only when regulation passes, thresholds are crossed, or technology matures.
  • Broken Assumption Detection: Surfaces baseline entries now contradicted by evidence, since strategy was built on them, and flags never-moving entries as furniture for retirement.
  • Structured Delta Report: Emits a fixed schema with run header, per-factor deltas, broken assumptions, new-to-frame factors, and strategy implications with Fact/Inference labels and citations.
  • Use Case: A product manager pastes last quarter's PESTEL for an EU payments product and suspects a new AI liability directive matters; the Skill checks the suspected event first, diffs all six factors, and returns a half-page report naming which assumptions broke and what to watch next cycle.

Quick Start

Run a PESTEL delta against my attached Q1 analysis for our EU payments product, and check whether the new AI liability directive changes anything.

Frequently Asked Questions about pestel-delta-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a PESTEL analysis up to date quarterly?

Run a delta scan against your prior PESTEL baseline instead of rewriting it. The monitor diffs each of the six factors, reports only material movement such as passed regulations or crossed thresholds, and keeps quiet factors to a single line each.

What counts as material movement in a PESTEL re-scan?

Material movement means regulation passed or credibly proposed, macro indicators crossing thresholds your baseline named, technology maturation with adoption evidence, or social signals backed by data. Think-pieces and stalled proposals do not qualify.

Can I run a PESTEL delta without a prior analysis?

No, a baseline is a hard prerequisite because there is nothing to diff without one. The Skill recommends running a full pestel-analysis first and stops, and it also refuses to diff across a scope change such as a new market or pivot.

What are broken assumptions in a PESTEL delta report?

Broken assumptions are baseline entries now contradicted by evidence, such as an assumed stable tariff schedule that was just revised. They outrank new observations because existing strategy was built on them, and each is traced to its baseline entry ID.

How does PESTEL delta monitoring differ from a full PESTEL analysis?

A full PESTEL builds the initial macro baseline from scratch, while the delta monitor re-scans that baseline on a cadence and reports only what changed. The pair turns PESTEL from a one-time workshop artifact into an operating radar.