Pestel Delta Monitor

Add skill

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.

Permissions

Files

SKILL.md

pestel-delta-monitor

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.

argument-hint: [prior PESTEL analysis, and any suspected events since]
intent: Refresh a PESTEL analysis by diffing each factor against the prior run and reporting material movement only — regulation passed, thresholds crossed, technology matured, assumptions broken. Macro factors move slowly; the value is catching the two that moved, not re-debating the twenty that did not.
type: workflow
theme: market-intelligence
best_for: Keeping a PESTEL analysis alive on a quarterly cadence instead of letting it rot in a deck, Catching which macro assumptions your strategy quietly depends on — and which just broke, Feeding regulatory and macro shifts into roadmap and OKR conversations with citations
scenarios: Here's the PESTEL we did in Q1 — what's moved since?, A new regulation just passed in our space; re-run the macro scan against our baseline
estimated_time: 15-30 min per run

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 first and stops — there is nothing to diff. (That referral is the empty-handed path: you leave knowing exactly what to do first.)

4 files · 23 KB10 KB

Version history

Pestel Delta Monitor

PESTEL Delta Monitor

Purpose

Input

Key Concepts

Application

Output schema (do not reorder)

Final Step (offer exactly 4 options)

Examples

Legal: moved

Common Pitfalls

References