All skills
deanpeters avatar

/pestel-delta-monitor

@eb7a51e

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/pestel-delta-monitor

This session only. Nothing lands on disk.

template.md

≈603 tokens on demand. Your agent reads this file only when SKILL.md points to it.

PESTEL Delta Report Template

Copy this for each quarterly re-scan. This monitor requires a baseline — a prior pestel-analysis output to diff against; never diff across a scope change. Report material movement only: regulation passed or credibly proposed, thresholds crossed, technology matured with adoption evidence. Broken assumptions are the real output — one baseline entry now contradicted by evidence outranks ten new observations, because strategy was built on it.

Real URLs and dates on everything — invented regulation is this domain's signature fabrication risk.

Template

# PESTEL Delta Report

## 1. Run Header
**Scope (from prior analysis):** [copy it — if scope changed, run a fresh pestel-analysis instead]
**Prior analysis date:** [YYYY-MM-DD]
**This run date:** [YYYY-MM-DD]

## 2. Factor-by-Factor Delta
_Keep "no material movement" factors to a single line each — the discipline is the product._

### Political: [moved / no material movement]
- **What moved:** [1-2 bullets, labeled, cited — only if moved]
- **Prior assumption affected:** [which entry from the baseline]
- **Reading:** [Inference — implication for the product scope]

### Economic: [moved / no material movement]
[same structure]

### Social: [moved / no material movement]
[same structure]

### Technological: [moved / no material movement]
[same structure]

### Environmental: [moved / no material movement]
[same structure]

### Legal: [moved / no material movement]
[same structure]

## 3. Broken Assumptions
- [Baseline entries now contradicted by evidence — the run's most important section; cited]

## 4. New to the Frame
- [Factors absent from the baseline that now warrant a slot]

## 5. So What?
- **Implications for strategy or roadmap:** [exactly 3 — label, confidence, URL where relevant]
- **Factors to watch closely next cycle:** [exactly 2]
- **Assumptions to validate:** [exactly 3]

Quality checks before you call it done

  • Every "moved" claim carries a real URL and date — regulations especially
  • Each delta names the baseline entry it affects — a delta with no "prior assumption affected" line isn't actionable
  • Quiet factors got one line, not a rewrite; a half-page report on a quiet quarter is the radar working
  • Baseline entries that never move and touch no decision are flagged as furniture for retirement at the next baseline refresh

Source: SKILL.md on GitHub

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured workflow for monitoring changes in PESTEL macro-economic factors. It follows professional intelligence-gathering practices and emphasizes factual citations. No malicious code or exfiltration patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at eb7a51e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago
argument-hint
[prior PESTEL analysis, and any suspected events since]
type
workflow
theme
market-intelligence
Other metadata
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.
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

README badge

README badge for deanpeters/product-manager-skills/pestel-delta-monitor