Pestel AnalysisSAFE

Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: pestel-analysis
argument-hint: "[product or market]"
description: Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.
intent: >-
  Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.
type: component
theme: market-intelligence
best_for:
  - "Scanning external forces before committing to a strategy or roadmap"
  - "Naming the macro assumptions your plan quietly depends on"
  - "Preparing the environmental context for a strategy review"
scenarios:
  - "We're setting next year's strategy and haven't looked at external forces in a while"
  - "New regulation is coming and I need to map what else could shift underneath us"
estimated_time: "30-45 min"
---


## Purpose
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.

This is not internal analysis—it's outward-facing assessment of the big-picture forces shaping your product's environment.

## Input

**Works best with:** The product, market, or strategic decision the analysis should serve.
**Also useful:** Geography, time horizon, and which forces you already suspect matter most.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The skill asks what product/market and geography to analyze before scanning the six forces — an unanchored PESTEL is a trivia exercise.

**Example invocation:** `PESTEL for launching our telehealth platform in Germany over the next 18 months.`

## Key Concepts

### The PESTEL Framework
Originating from Francis Joseph Aguilar's 1967 PEST analysis, PESTEL extends the framework to six categories:

1. **Political:** Government policies, stability, trade regulations, taxation
2. **Economic:** Growth rates, inflation, exchange rates, consumer spending
3. **Social:** Demographics, cultural trends, lifestyle changes, consumer attitudes
4. **Technological:** Advancements, R&D, automation, digital transformation
5. **Environmental:** Climate change, sustainability, resource scarcity, regulations
6. **Legal:** Compliance, IP rights, employment laws, health/safety regulations

### Why This Works
- **Comprehensive:** Covers all major external forces affecting your product
- **Proactive:** Identifies threats and opportunities before they become critical
- **Strategic:** Informs long-term planning, not just tactical decisions
- **Risk management:** Highlights vulnerabilities in your product strategy

### Anti-Patterns (What This Is NOT)
- **Not competitive analysis:** PESTEL looks at macro factors, not competitors
- **Not internal analysis:** Focuses on external environment, not your company's strengths/weaknesses
- **Not static:** Macro environment changes—reassess regularly

### When to Use This
- Entering a new market or geography
- Strategic planning (annual roadmapping, 3-5 year planning)
- Assessing product viability in a changing environment
- Risk assessment for new product initiatives
- Pitching to execs or investors (shows environmental awareness)

### When NOT to Use This
- For tactical, short-term decisions (use competitive analysis instead)
- When external factors are stable and well-understood
- As a substitute for customer research (PESTEL is macro, not micro)

---

## Application

Use `template.md` for the full fill-in structure.

### Step 1: Define the Scope

Clarify what you're analyzing:

```markdown
## Overview

- **Project/Product Name:** [e.g., "AI-Powered Invoice Automation for SMBs"]
- **Analysis Purpose:** [e.g., "Assess viability of launching in EU market"]
- **Analyst:** [Your name or team]
- **Date:** [Date of analysis]
- **Geographic Scope:** [e.g., "United States and European Union"]
- **Time Horizon:** [e.g., "Next 12-24 months"]
```

**Quality checks:**
- **Specific:** Not "analyze market" but "assess viability of EU launch"
- **Time-bound:** PESTEL factors change—state your horizon

---

### Step 2: Analyze Political Factors

Examine government and regulatory influences:

```markdown
## 1. Political Factors

### Government Policies
- [How could government policies impact the product?]
- [Example: "EU's AI Act requires transparency in AI decision-making; our invoice automation must explain recommendations"]

### Political Stability
- [Assess stability in relevant regions]
- [Example: "US political stability is moderate; potential for regulatory changes in financial tech under new administration"]

### Trade Regulations
- [Examine trade regulations and their effects]
- [Example: "Brexit complicates data transfer between UK and EU; may require separate infrastructure"]

### Taxation Policy
- [Analyze taxation policies and implications]
- [Example: "Digital services tax in EU (3% on revenue) could impact pricing strategy"]
```

**Quality checks:**
- **Specific to your product:** Don't list generic policies—explain the impact
- **Actionable:** Can you adjust strategy based on this insight?

---

### Step 3: Analyze Economic Factors

Examine economic conditions:

```markdown
## 2. Economic Factors

### Economic Growth
- [Evaluate growth rates and their impact]
- [Example: "SMB sector growing 5% annually 

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.